Piraxus / OrbiterSkyboltClient

Skybolt Engine graphics client for Orbiter Spaceflight Simulator
MIT License
14 stars 4 forks source link

Random crash when scenario editing to Venus #4

Open OvalDreamX opened 1 year ago

OvalDreamX commented 1 year ago

It was just for testing. And while there are some obvious issues when going far from earth (even on mars), like everything going black except for the 2d elements (mfd, hud, menu, etc) as seen on the image, I understand it may still be too soon. Still, this random crash may have something that can help you image

matthew-reid commented 1 year ago

There are some precision issues when traveling far from a planet which I need to fix.

Venus uses the old style Orbiter terrain (.tex files) instead of the newer tile tree files used by Earth, Mars, Moon, and a few other planets. I haven't added support for the old terrain format which is probably why it's crashing. Is the crash reproducible? If so which scenario did you run? When I run the Venus DG scenarios it runs but the planet does not show.

OvalDreamX commented 1 year ago

Unfortunately I havent been able to reproduce the error. It happened when teleporting via scenario editor to venus (from habana scenario I think). After seeing everything went black after some seconds of invisible planet case, I f1 to the glass cockpit and there was the crash. Will try to reproduce it later. Maybe Ill be able come back with more useful info haha

matthew-reid commented 1 year ago

If the crash happens again and you get the Debug Error dialog, you can click Retry (or Reintentar for you) and it should open up an instance of Visual Studio and show the source file and line number where the crash occurred, which is useful information.

Incidentally, I see that you're running the Orbiter visual studio debug build, which is good for debugging but is going to run slower than the release build. So, if the performance is too bad, I'd recommend switching to the release configuration in Visual Studio.

OvalDreamX commented 1 year ago

Tnxs, will try to get which line has the problem. And thanks or the tip, visual studio is still kinda unknown territory for me