Search results

STS-61

Ah ok I just tried setting the launch time on the Launch tab to 12:02:59 instead of 12:03:00 (the troublesome time) and it fixes the issue. Here is the json file with the unmodified launch time: https://www.dropbox.com/scl/fi/1hwr4ri54rpq5xiuh3m59/STS-41G.json?rlkey=4kkgszhyo92zu2o3mxnmiu75f&dl=0

I tried removing one second in the scenario export page, but that still gives a T-31second start point in the sim, so I manually removed 1 second from the 41G scenario's MJD and that made it start at T-32 seconds in the sim...and the problem did not occur.

Aha! It works when I do it that way, without changing anything else.

I had the log already attached to my previous post, or do you mean something else? It does not happen with the Launch Test scenario, it seems to just happen on scenarios I create with the ME. I am running Orbiter 2016 and SSV 1.7.

Here's what the log says: (SSV_LCC) [INFO] RS Countdown Hold Flag is on @ T-26.990 000016.869: (SSV_LCC) [INFO] LPS Go For Auto Seq Start Hold 000016.869: (SSV_LCC) [INFO] Cutoff https://www.dropbox.com/scl/fi/m9twdwnt80nu6r8kgh7cl/Orbiter.log?rlkey=aobh58rml0bzsvzthuyxdtnnu&dl=0 Hmm, there...

Hello, I have a small issue when creating T-31 second scenarios with the mission editor: When running the scenario, the launch holds at T-27 seconds. Its weird because on ~10% of the times it does pass through to liftoff, so seems like it may be a bug. Here is a scenario where the issue happens...

The debug string is still updating with Mode Sel > Ldg Radar, except for the altitude and altitude rate. This is because those are read directly from lgc_alt & lgc_altrate in RadarTape class and unfortunately are only updated with the switch set to PGNS. On Apollo 11 I think the checklist...

Are your cabin fans on?

Mission control support is now available for Apollo 12. As said before this will not be an officially supported MCC mission for NASSP 8 release but I will try my best to keep it up to date with the latest RTCC state. Functionally the same as Apollo 11 MCC tracking plus a few extra features...

Apollo 16 on pad 39A April 16, 1972. Target: Descartes Highlands

I personally prefer the solution where shadows are not baked in. As said above, D3D9 already does quite a good job at depicting the outside view shadowing so if the same can be brought to the VC that is the best solution in my opinion.

@Felix24 Looks very impressive! Are you modifying the mesh in your work or just the textures? If its just the textures then there hasn't been any changes to them since July, but in any event, is it possible for you to work from the latest NASSP version? There has been murmurous small fixes to...

Looks good! I think it might be easiest if I just make a new sphere myself in Blender and post an updated VC mesh with it on here. Im on the road right now, but should be able to have it within a few days.

I think the DDS file for the FDAI is somehow a different type of DDS then the others...not sure right now what the exact compression/format the file is other than being 24 bit. Once I get back to my main PC I will take a look at it more closely. About the higher definition ball, do you use...

It looks awesome! Yes you can finish it, with 2 versions if that works for you (1024x512 and 1800x900) Also as I said in the git post, we'll need a set of the textures without the red areas (for the LM) Thanks!

Thanks for the modified files! There seems to be good results with using two versions of the textures in NASSP: Virtual cockpit: Original 1024x512 with no blurring 2D cockpit: 1024x512 with light blurring This seems to be a good compromise...the pull request has been amended with these changes.

@Lupus_Vulpes Thanks for the files! A pull request is open for this: https://github.com/orbiternassp/NASSP/pull/692 The textures are great in the 3D cockpit but unfortunately in the 2D cockpit it is a bit grainy/pixelated so we would like to use a modified version just for the 2D cockpit using...

In the Two Impulse page, do you have the parameters set correctly? With the OFF button you should type in: P51,15,1.7,26.6,130; This is what the page should look like: (BTW, this is an Apollo 14 testing scenario so the T1 & T2 times are not correct here, T1 should be insertion + 3 minutes & T2...

Thanks! I will try and give it a test once I get a build environment going for Orbiter.