getting CTD on subsequent scenario starts
Restarting a simulation without closing launchpad is unsupported so far.
I'll try to find a way to support it.
If you start Orbiter without module on, enable then disable the module right away , and start a scenario, would there be a CTD?
And I keep on having this CTD, too.
Seems to be linked with the restart scenario CTD.
The way this work, you can't just reinitialize it without a program restart.
I would have to redo it from scratch, or get Martins to put it into the core.
Here's what I found. - People with Data Execution Prevention turned on for all applications, i.e. "/NoExecute=OptOut", should have the same problem with videnie as me (for both debug and release modules).
64 bit Win 7 here, turned on DEP, no crashes, no clues. And the only laptop with WinXP in immediate vicinity won't be back from repairs until a few weeks later.
I'll keep an eye for it for the moment.
Might be something simple, might be something else.
if the simulation is closed while "Panning Mode" is ON, then videnie module is disabled in OrbiterLaunchpad, then restart the (current state).scn, it gives a CTD.
Same problem i had with Orulex and other dummy-vessel-exploiting addons - no way to exclude a vessel from a save.
However, there is no need to crash on this thing, actually - i have no idea why i got that idea of using a module for something that could be done by a plain cfg!
Please try this one (enable module first to regenerate the cfg):
I don't understand why the "Target" vessel is neccesary (but I'm sure you have a good reason to do it this way!) - When making the Vega spacecraft "camera-tracking" function, I had to make some code to stop this panning effect when in external view - so I think it may be possible to implement this effect without using an extra vessel.
Full stop, would you say that again and with details, please?
I've tried it, and there were almost no problems. All I found was that the very first time I ran it, orbits of outer planets were looking as if they were on highly eccentric hyperbolic orbits
but after starting another scenario, they looked perfectly normal. Also, the first time panning mode caused a CTD upon activation, but again, the next time it worked fine.
Can you reproduce either of them from a clean install?
Was that with 101005 version?
What about 101007 above?
a problem with planet orbits being drawn over planets even when they're supposed to be hidden
There is no Z-buffer for planets in Orbiter, so i have to clip lines manually.
Only the reference body is accounted for, however, for performance reasons.
For planets that's the Sun.
May add an option, if it's worth the lost FPS for somebody.
could it be possible to have a section in the CFG where one could manually override the display parameters for any given-named objects?
On the list.