Board index FlightGear Development Spaceflight

Space Shuttle - Bugfixes

Discussion about development and usage of spacecraft

Re: Space Shuttle - Bugfixes

Postby GinGin » Sun May 02, 2021 10:20 pm

I looked of course to the pointed line :)
And I don't see the culprit.
GinGin
 
Posts: 1580
Joined: Wed Jul 05, 2017 11:41 am
Location: Paris
Callsign: Gingin

Re: Space Shuttle - Bugfixes

Postby wlbragg » Sun May 02, 2021 11:07 pm

@GinGin can you post your entire log. Sometimes a different nasal error can cause a faulty or misleading cascade type error.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7586
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: Space Shuttle - Bugfixes

Postby GinGin » Mon May 03, 2021 3:53 pm

@wlbragg: Sure, I will ask to the concerned persons about their logs.
GinGin
 
Posts: 1580
Joined: Wed Jul 05, 2017 11:41 am
Location: Paris
Callsign: Gingin

Re: Space Shuttle - Bugfixes

Postby Thorsten » Mon May 03, 2021 6:04 pm

And I don't see the culprit.


Neither do I - though sometimes it's a missing tag which does not close something above, I've just had a quick look...
Thorsten
 
Posts: 12490
Joined: Mon Nov 02, 2009 9:33 am

Re: Space Shuttle - Bugfixes

Postby eatdirt » Mon May 03, 2021 7:47 pm

May 2020, do you remember how did you get rid of it ?


Yes, that's just in the post following my comment :)

Arf, my mistake, I was confused by a commit dated from the 7th of May 2020 and I've tested the "master" branch instead of the devel one.


That's why! I was just cloning fgspaceshuttle, which sets the default branch to master. So, you have to

Code: Select all
git checkout development


before doing anything else. I think I made that comment to Gomendio on the devel thread, it is very easy to make that mistake. Now, if this is happening with the --launcher, we may have a problem indeed. But again, it is very easy to have a version of the Shuttle installed in a directory that would take precedence over the one installed by the --launcher with some .fgfsrc settings?
eatdirt
 
Posts: 1012
Joined: Wed Aug 15, 2018 3:06 pm

Re: Space Shuttle - Bugfixes

Postby GinGin » Fri May 07, 2021 5:59 pm

That's why! I was just cloning fgspaceshuttle, which sets the default branch to master


Thanks, though they installed the stable version from the FG launcher.


it is very easy to have a version of the Shuttle installed in a directory that would take precedence over the one installed by the --launcher


Interesting point.
I didn't have feedback from their logs yet, so nothing to investigate more for now.
GinGin
 
Posts: 1580
Joined: Wed Jul 05, 2017 11:41 am
Location: Paris
Callsign: Gingin

Re: Space Shuttle - Bugfixes

Postby wlbragg » Fri May 21, 2021 7:19 am

Well here's a new one. I thought this might be Chris's new work but it is happening with my original before I merged the new RMS rotations and it only is happening with a relatively recent build of next. If I run a 2020.4 nightly I have from a couple months ago I don't get the error. So far it is only the Shuttle I am seeing this with.
I will probably have to take this to the dev list as I think it is something new or changed in the core but I thought I would post here first just in case someone has seen this.

The last logged lines are ...
Code: Select all
Trim Results:
       Angle of Attack:    7.5  wdot:  2.80e+01 Tolerance: 1.000000e-03  Failed
              Throttle:    0.5  udot: -2.06e-01 Tolerance: 1.000000e-03  Failed
            Pitch Trim:      0  qdot:  3.48e-10 Tolerance: 1.000000e-04  Passed
            Roll Angle:  0.023  vdot: -1.11e-02 Tolerance: 1.000000e-03  Failed
              Ailerons:      0  pdot:  6.75e-08 Tolerance: 1.000000e-04  Passed
                Rudder:      0  rdot: -1.26e-06 Tolerance: 1.000000e-04  Passed

  Trim Statistics:
    Total Iterations: 61
    Sub-iterations:
    wdot: 0 average: 0  successful:  0  stability: 2
    udot: 0 average: 0  successful:  0  stability: 2
    qdot: 0 average: 0  successful:  61  stability: 2
    vdot: 121 average: 1.9836  successful:  61  stability: 2
    pdot: 0 average: 0  successful:  61  stability: 2
    rdot: 0 average: 0  successful:  61  stability: 2
    Run Count: 2210


Anyone have any idea what this is, Thorsten?

Image
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7586
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: Space Shuttle - Bugfixes

Postby Thorsten » Fri May 21, 2021 10:06 am

No, sorry.
Thorsten
 
Posts: 12490
Joined: Mon Nov 02, 2009 9:33 am

Re: Space Shuttle - Bugfixes

Postby jano » Fri May 21, 2021 8:55 pm

same here, both Vostok and the shuttle are not starting:

Image
jano
 
Posts: 221
Joined: Fri Nov 30, 2007 12:32 am
Location: france
Callsign: jano
Version: git
OS: debian SID

Things I noticed

Postby VA-41 » Sat Mar 18, 2023 4:13 pm

So I made this list of things I came across thinking that they were bugs/incorrect behavior (compared to the real life shuttle) and GinGin recommended sharing it here too.


List version 5

DPS
  • "ON" in "SERC ON" should be "double overbright". [DPS dict 3-6]
  • SPEC 63 should not be able to be accessed in GNC OPS 2. [DPS dict 3-1]
  • Some other item entries than PEG 7 are also supposed to "unload" the burn data. [DPS dict 3-8]
  • PEG 7 Z axis is reversed. [SCOM 2.13-3 & SCOM 2.18-2]
  • It should be possible to go from MM104 to MM602, possibly instead of MM601. [DPS dict 1-2]
  • It seems like the DPS should not go from MM102 to MM601 before SRB SEP. [DPS dict 1-2]
  • Instead of emptying, the scratch pad line should only stop blinking on command termination. The static line will fully empty by starting a new command, pressing the CLEAR key, or changing the major function. [SCOM 2.6-37]
  • On MNVR displays, TV ROLL can only be changed in MM202. [SCOM 2.18-2 & DPS DICT 3-7]
  • GPC fail votes should cause master alarm, GPC C/W light and a DPS fault message. [SCOM 2.6-6]
  • When major mode changes (with no OPS transition), both SPECs and DISPs are retained. [SCOM 2.6-32 & Software Interface WB 4-4]
  • SPECs are retained inside their own major function when another major function is selected. DISPs are not retained. [SCOM 2.6-32 & Software Interface WB 4-4]

INSTRUMENTS
  • On entry, the yaw error needle should display estimated sideslip. [DPS dict 6-20]
  • On ascent, the HSI does not have the N, E, S and W symbols. [SCOM 7.1-3 & DPS DICT 6-14]
  • In entry mode (not TAEM or A/L), the compass card should indicate the relative velocity vector instead of heading. [SCOM 2.7-10 & SCOM 2.7-11]
  • The HSI should have a "lubber line". [SCOM 2.7-8]
  • RCS COMMAND YAW light should function like normal throughout entry, ROLL and PITCH lights have different functionality after qbar 50. [SCOM 2.22-16 & SCOM 2.7-19]
  • The SENSE switch should affect the ADI in addition to flight controls. [SCOM 2.7.6]
  • On-orbit ADI rate scales are HIGH: 5, MED: 1, LOW: 0.2. [SCOM 2.7-7]
  • Pressing the ATT REF pushbutton should apparently set a new reference for the "REF" ADI mode. [SCOM 2.7-4]
  • The ADI ball does not show yaw on ascent pre-MECO or on entry. [SCOM 2.7-4]

GUIDANCE
  • On RTLS Nz hold is always 2.2 G. [SCOM 6.3-7]
  • If ECAL/BDA logic is not active during contingency aborts, TAEM should not be entered automatically. [CONT ABORT WB 4.10.7 & CONT ABORT WB 4.14.19]

FLIGHT CONTROLS
  • On ascent, selecting CSS on either axis should give CSS to both axes. [SCOM 7.1-7]
  • Yaw jets are used until Mach 1. [SCOM 2.13-55 & SCOM 2.22-17]
  • Pushing the CONTROL FREE button should switch all the rotation axes to ROTATION PULSE. [SCOM 2.13-50]
  • Deflecting the RHC past the soft stop should cause continous jet firing in DISC RATE as well, not only in PULSE. [SCOM 2.13-50 & SCOM 7.2-5]
  • In transition DAP, it should possible to switch between ROTATION DISC RATE and PULSE. [SCOM 2.3-51]
  • None of the ORBITAL DAP button lights should be operational during ascent or entry. [SCOM 2.13-48]
  • The CSS/AUTO and MAN/AUTO button lights extinguish after SSME zero thrust (except the body flap light, which is used to indicate dump status). [SCOM 7.1-4]


The square brackets have the "sources" I used as manual pages. Please correct me if I'm wrong about any of these.

EDIT: I'm updating this message as I update the list. Italics mean changes from last update, and strikethrough means the feature has been implemented.
Last edited by VA-41 on Sat Mar 09, 2024 7:20 pm, edited 5 times in total.
VA-41
 
Posts: 46
Joined: Sun Nov 15, 2020 7:30 pm

Re: Space Shuttle - Bugfixes

Postby GinGin » Thu Mar 23, 2023 1:01 pm

Thanks.
Working on some items.
GinGin
 
Posts: 1580
Joined: Wed Jul 05, 2017 11:41 am
Location: Paris
Callsign: Gingin

Possible hud alignment issue

Postby VA-41 » Wed Apr 26, 2023 7:21 pm

While I was testing adding aim point markers to the scenery, I noticed that this is what it looks like on the HUD with autoland on:
Image

It appears to aim short of the marker. However, if I take a look at the recording of the approach with Tacview, the flight path vector appears directly on this marker that should have the same coordinates as the one in the scenery:
Image

I wonder, is the HUD somewhat off compared to the scenery, or have I made some sort of mistake with the marker placement and the recording.
VA-41
 
Posts: 46
Joined: Sun Nov 15, 2020 7:30 pm

Re: Space Shuttle - Bugfixes

Postby Thorsten » Thu Apr 27, 2023 9:58 am

I wonder, is the HUD somewhat off compared to the scenery, or have I made some sort of mistake with the marker placement and the recording.


To get the obvious out of the way - the HUD shows the current NAV state vector of the Shuttle, not scenery - to the degree that the state vector is drifted, it can be substantially off.

So what was the quality of your state vector?
Thorsten
 
Posts: 12490
Joined: Mon Nov 02, 2009 9:33 am

Re: Space Shuttle - Bugfixes

Postby VA-41 » Thu Apr 27, 2023 1:05 pm

So what was the quality of your state vector?

I had perfect navigation on for that approach.
VA-41
 
Posts: 46
Joined: Sun Nov 15, 2020 7:30 pm

Previous

Return to Spaceflight

Who is online

Users browsing this forum: No registered users and 4 guests