Saturn IB second stage not igniting

[buzzbenz]

Having a rather bizarre issue here.... On my main gaming PC, when i try the Saturn-IB / Skylab mission, the 2nd stage (S-IVb) will never ignite. I have been trying to troubleshoot this issue for days now, and i am pulling my hair out trying to figure out what is happening. The mission starts fine, up to the launch and the launch itself work fine, but once staging occurs, nothing else happens. No ignition of the next stage, no automatic tower jett, nothing. I just eventually fall back to Earth and explode (well, unless i abort and eventually deploy the chutes and whatnot of course :) ).

I have unmapped my controller, and reset all input, panel states, and checklists back to default more than once. I have uninstalled / reinstalled, uninstalled and reinstalled to a different drive, uninstalled / reinstalled back to the original drive, and have now gone as far as uninstalling, disabling saving on Steam, deleting the Wilhelmsen Studio folder in my Appdata/Local Low folder, deleting the Wllhelmsen Studio registry entries, deleted any reference to game 882140 in any and every Steam folder i could find it in, rebooting the machine, reinstalling, enabling the Saturb-IB / Skylab Alpha feature (the misspelling is actually in the game that way :D ). and then restarting the game, just to have the S-IVb stage STILL not fire and the spacecraft fall back to Earth.......

Now, if that is not odd enough - when i installed this on my older PC that's been relegated to family use ---- IT WORKS JUST FINE! Both machines are Win 11 Pro installs, both are i7 based processors, both have nVidia video cards. Windows updates are current on both machines, driver version for the GPU is actually newer on my main gaming rig. Windows install on the older PC is pretty new since i reformatted it after i moved to this newer PC.

The ONLY other thing i am finding odd is this... During the launch, some astronaut comms seem "off"... For instance, it says something about "roll program complete, beginning pitch program" before the roll program is actually complete, and after the Abort mode 1C (i think - it's the one at 1:54), the next messages stating "inboard cutout / go for staging" almost overlap each other before the 2:00 min mark if i recall correctly..... I don't recall that happening quite the same way on the PC that this is working on.

Looking for any help anyone can offer! I am at my wits end trying to figure out what's happening, and i am at a total loss as to what may be causing this at this point, unless there is some subtle architecture difference between a 12700k and a 13700k CPU that would cause Unity to behave a bit differently...........

[LyraCreative]

That does indeed sound very strange! Would you be able to share the logs with me? And are you on my Discord Server for the game?

[buzzbenz]

i have been on the discord once or twice but i'm not exactly familiar with it... I can provide logs, i just need to know what to do to get them to you, and which ones you need. I had turned the analytics off, but if needed i can turn them back on and run through it again, i have that launch checklist about memorized by now so i can run through that real quick now :D

[LyraCreative]

Hi!
If you load up the game and reproduce the issue, and once the staging does not work, let it run for another 10 seconds and close the game.

When the game is closed, you can send me the Player.log file to [e-mail]. This log contains the data from the most recent game session.

Thanks!

[buzzbenz]

Log sent! Thanks for checking into this, hopefully some answer can be found!