SSU version 2.0 public alpha release bug report thread

[Poscik]

Just TARGET_VESSEL ISS.

 

[Ender]

CRT Puzzle !!

Maybe not the right forum for this question, but then again maybe I'm the "Bug" in this case..:idk:

Can somebody give me a hint, on how to get the CRT's to work.
I know about the checklists, but i have no clue of what the displays should display.

In the launch scenario's, i activated the CRT from the mfd.menu, but then it is blank.
It shows what i'm punching in, but at "PRO"it does not proceed and only shows the tekst.
There is a good chance that i'm punching in something wrong, but wouldn't there be an error message then ??, now it just does nothing.
Maybe in that case somebody can give me something usefull to enter just to test if i can get an OPS screen visible before the launch.

It also would help if i knew what the display config in the cockpit should be before launch, and what they should display.

I think it is impossible to do it just by checklist's, specially if i don't know what is working or not in this release.

Hope someone can help me out,

Greets

 

[Poscik]

First visible display is OPS103. It should appear just after ET separation.

 

[DaveS]

First visible display is OPS103. It should appear just after ET separation.

That should be MM104, not MM103. 101 is pre-launch, 102 first stage ascent, 103 second stage ascent and 104 is OMS1 MNVR EXEC.

 

[DaveS]

crashed at deimos loading

I refer you to post#1: http://www.orbiter-forum.com/showthread.php?p=447618&postcount=1

 

[kamaz]

Hello,

SSU2.0 can be crashed by calling clbkLoadStateEx().

The attached add-on and scenario demonstrates the issue.

 

[SiameseCat]

Hello,

SSU2.0 can be crashed by calling clbkLoadStateEx().

The attached add-on and scenario demonstrates the issue.

I don't think this is a problem. clbkLoadStateEx loads the state from a scenario file during initialization. In the code you've attached, clbkLoadStateEx is called during the simulation, after initialization. This is not the time at which clbkLoadStateEx should be called, and it's not a problem if a CTD occurs.

 

[kamaz]

I don't think this is a problem. clbkLoadStateEx loads the state from a scenario file during initialization. In the code you've attached, clbkLoadStateEx is called during the simulation, after initialization. This is not the time at which clbkLoadStateEx should be called, and it's not a problem if a CTD occurs.

Well, it is a problem if you are attempting to replicate vessel state between two instances of Orbiter, which is what I am doing: http://orbiter-forum.com/showthread.php?p=451291&postcount=25

 

[SiameseCat]

Well, it is a problem if you are attempting to replicate vessel state between two instances of Orbiter, which is what I am doing: http://orbiter-forum.com/showthread.php?p=451291&postcount=25

Trying to replicate state by saving/loading a scenario file won't work with SSU. Among other possible issues, the GPC state isn't fully saved during launch and OMS burns, so these won't be handled correctly when the saved scenario is loaded in another Orbitersim instance.

 

[STS]

Hello

Talking about last public SSU release (2.0):

After landing rollout, at wheels stop, Orbiter MFD´s stop working, not updating and unable to interact with them. The same applies to HUD. Didn´t test if this happens also on glass cockpit view.

Seen in installation with SSU+DGIV+XR Vessels and in clean SSU install.

 

[SiameseCat]

Can you reproduce this using the built-in graphics client (orbiter.exe)? I can reproduce the issue using the DX9 client, but not the built-in graphics client.

 

[STS]

Thanks.

Will try tonight.