SSU version 2.0 public alpha release bug report thread

[Donamy]

They never reached orbit. It's all a hoax.

 

[1hippienaut]

need to make sure this isnt
just on my end
all is working great save for 2
points no switch movement
except pldbay r11,crt panel switches
and flt cntrl pwr
dap functions hold bearing
well
noted
no nose rockets during
pointing
with item 19 or 18
everything seems set up right
though cant move some of the apu switches
many do
hoping i installed everything right

 

[1hippienaut]

not sure where to post this issue
forgive me if this is a procedure question
just let me know
and it wont happen again
still no luck with rcs firings
also noticed spec 34 has no screen in crt
and cant edit spec 20 items
not sure what i did wrong
havent had any ctds
involved so not sure what a log file
would help though i can post one
if needed
do i need to power them on
via switch
seems the rates are very slow as well
im running sts-1
"on orbit"
am i missing a new manual?
no rush
i know yall are busy on all sides
doing a fine job

---------- Post added at 09:10 AM ---------- Previous post was at 12:46 AM ----------

all a go
repeat all a go
updated again thru svn to rev. 1559
issue closed

 

[1hippienaut]

so are the animations for arm/press not working?
when i go to move them from off
they just bob a little
still cant fire oms no help from manuals
also wondering what code bits in
.scn file do i add for iss tracking
in spec 34 and ops 202
i also get an overflow message
i do understand i need to be set up
align plane wise
before rendezvous
basically just the arming and firing of
Thanks in advance

 

[Poscik]

As
I
said
earlier,
refer
to
original
nasa
checklists.
If
you
want
to
press
enter
and
fly,
then
use
Shuttle Fleet.

 

[1hippienaut]

Thanks for your reply
im familiar with the checklist process
and looking forward to more updated system functionality
so now in light of the new alpha 2.0 release
what changes are now active in systems
my question was more about
what is currently usable from check list specifically
i know how to execute the process
i assume your saying to fire them
i must follow the steps
leading up to and including switch flipping
not a problem as its mostly crt work i like the screens
so about the iss tracking
through entry into scn

what should we enter so as to attain a target
do the arm/press switches function
in some of the scenarios it says Loms Roms
is set to Off
if i cant arm/press the LR oms then how do i ask dap
to auto fire them
as in the rendezvous test scn
and spec 34
which has a target specified in scenario
again Thank you for your reply

:tiphat:

 

[Poscik]

Arm/press OMS switches are "pull and move", so you basically need to hold LMB and move the switch, then release. To start the burn, you have to press EXEC 15 seconds before TIG (exec starts flashing on the bottom of the screen).

About rendezvous, if you see example entry in scenario that sets rendezvous target, then where is your problem now? Can't you just copy paste and change target name to match your own wish?

 

[1hippienaut]

thats it :facepalm: Thank you

@SUBSYSTEM SimpleGPCSystem
  @BEGINSOFTWARE OrbitDAP
  TGT_ID 2
  BODY_VECT 5
  ROLL 0.000000
  PITCH 0.000000
  YAW 0.000000
  P_ANGLE 90.000000
  Y_ANGLE 90.000000
  OM_ANGLE -1.000000
  DAP_MODE 0 0
  ROT_MODE 0 0 0
  TRANS_MODE 0 0 0
  CONTROL_MODE 1
  @ENDSOFTWARE 
  [B]@BEGINSOFTWARE StateVectorSoftware
  TARGET_VESSEL ISS
  @ENDSOFTWARE [/B]
  @BEGINSOFTWARE OrbitTgtSoftware
  TIG_T1 1 18 30 0.0
  DT 60.000000
  RELPOS_T2 0.000000 0.000000 0.600000
  BASE_TIME 0 0 0 0.0
  @ENDSOFTWARE 
@ENDSUBSYSTEM		;SimpleGPCSystem

all of this or just the iss part in the state vectors lines

Take care

 

[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.

 

[1hippienaut]

what does this mean
Error: MDU 9 Text Buffer Overflow
i enter item 28 in spec 34
display T1 numbers appear as normal
i then hit resume
as soon as i key in item 22
in the ops 202 screen the error occurs

also how do turn off the null rate read out at the bottom left
of screen
couldnt find the hot key in the reference

 

[1hippienaut]

should i have posted my above
question in a different
thread
or do i start a new thread of question
still trying to get my sea legs
around here
:facepalm:
i sure appreciate yalls patience

 

[1hippienaut]

crashed at deimos loading

 

[DaveS]

crashed at deimos loading

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

 

[1hippienaut]

wrong thread :facepalm:
Cheers

 

[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