Universe Sandbox

Universe Sandbox => Universe Sandbox ² | Support & Bugs => Topic started by: marcel on August 26, 2017, 01:09:42 AM

Title: Game Launch problem - Object reference no set to an instant of an object
Post by: marcel on August 26, 2017, 01:09:42 AM

Hi, I'm looking for help. Please give me advice what to do? My 6 years old son is playing this game ( and it will be very very painfull for him to loose it ( literraly, because he is autistic and big universe fun). Today we just can't lunch the game.

I already try:
- restart computer
- reinstall the game
- repair of microsoft visual
- DirectX update
- reinstall .NET 2

Any ideas?

Title: Re: Game Launch problem - Object reference no set to an instant of an object
Post by: SyzygyΣE on August 26, 2017, 01:26:34 AM

This issue has already been brought up over at the Steam forums (http://steamcommunity.com/app/230290/discussions/1/1471969431589982987/), and I believe it is a bug that slipped through in a minor update today. A fix shouldn't be too hard and shouldn't take more than 48 hours. Whatever update is next implemented to the game will almost certainly be a fix for this. In the meantime, I recommend you keep the game and wait for the devs to see what they can do about it.

Title: Re: Game Launch problem - Object reference no set to an instant of an object
Post by: emarksmi on August 26, 2017, 09:29:02 AM

That is what I like about this forum.  Quick, polite, accurate responses.

I obviously have the same problem and it was nice to see that it is already being addressed.

Title: Re: Game Launch problem - Object reference no set to an instant of an object
Post by: Jar on August 27, 2017, 04:22:39 PM

Sorry for the issue. This is now fixed. We just rolled back to Update 20.1.1 (the update before our 20.1.2 release on Friday that caused this issue).

If Steam doesn't automatically download this update, just restart Steam completely and it should download it.

As far as we can tell, this issue only affected Windows 7 users (which is why we didn't catch it when testing). We are looking into this now so we can resolve it for the next release. Sorry once again for the issue.