Search results

Please don't do that (unless the auto declutter function can be disabled by the user). IMHO it is good to have the chance to choose if and when to de-clutter the HUD; after all you should de-clutter only twice on final approach (first level when you have the RWY in sight and second one before...

Are you considering implementing an RPOP tool (like the one they used on their onboard laptop computer)? We had it for Orbiter 2010 (unfortunately it doesn't work with O2016) and it was a great aid in flying and monitoring precise proximity operations and flyarounds (plus the extra realism added)

In addition to XRSound.

Don’t know if this is related to Orbiter Sound since I have the same issues with SoundBridge module by dbeachy1 :shrug:

I am using Orbiter Sound. Tried the Sound Bridge but the issue remains

Cause I totally trust your ascent guidance system :lol: To be more clear the issue happens when I select another vessel (not just switching the view target) and even after replacing the .wav file with the originsl one

I thought it was an issue on my end only since I have some weird stuff happening with Orbiter sound. For example during first stage if I switch the view to another vessel (i.e. the ISS) and then go back to SSU view the engines sounds is gone (as if I was already in second stage) this doesn’t...

About the APU sound: I still hear them running when inside the Orbiter flight deck (internal view) This is not supposed to happen, right?

Thanks for the APU sound fix. Actually it is pretty cool to hear three different and indipendent units :thumbup: As far as the problem with guidance crashing the orbiter on approach did you fix this too? Cause I ran the KSC 15 scenario and SSU preflared and landed flawlessly..

I mean this issue with the new seams I made BTW with the new update there are 2 small bumps: 1 where the FRCS module merges with the nose (top nose section); the FRCS module overlaps the seal and part of the nose. And another one where the RCC "plate" merges with the belly tiles (lower nose...

Since Dave said he “customized” the mesh for the hi-res textures wouldn’t it be better using those to check against glitches?.. ---------- Post added at 02:46 PM ---------- Previous post was at 02:44 PM ---------- Would this solve also the nose cap seams issue?

Are you checking this with the deafault SSU textures? I can't see any seam issue in that area with my HI-RES ones

About adjusting for the errors and glitches above: with Non Spherical disabled it is just a matter of changing the launch time. Problem is how do we do that when Non Spherical is enabled. I wonder if there is a way to predict Nodal Regression at a future time (hence the magnitude of my desired...

In some missions OMS-2 burn attitude was Heads Up. So that means it was kind of pre-programmed in MM105?

Is it ok to use FDO MFD (0.1.9) with Non Spherical Gravity enabled? I am asking since I am checking it with STS-114 and I get an extremely high DV in the plan for the NPC burn. I am using the actual launch date/time with the ISS state vectors uploaded via the closest time available from...

Can you guys confirm the Orbiter mesh are finished and will remain this way in the future? If so I will go back to my hi res textures work Thanks

I noticed the TV ROLL in MM105 (OMS-2 burn) is stuck at 180 (Heads down burn attitude) I've tried loading ITEM6 +0 (or even +360) in order to have the Orbiter Heads up for the burn but I get an illegal entry message. I know we can tweak this value in MM202. Is there something I am missing or SSU...

I see. My Columbia (ORIG) and Challenger Textures are pretty much ready, just waiting fr the mesh to be done and finalized. The new OMS pods for the whole fleet are also ready. Here you can see the Black and the white tiles on the fwd section of the pods which I re-drawed from scratch in...

What about those two black “fangs” on left and right side of the FRCS? Issue with mesh/textures?

Correct. I haven’t added the P3/P4 truss yet, so it is up to 11A