Performance Issues with Starship – Sporadic FPS Drops
-
@Black-Square Hello, The actual version is V0.1.1 ?
@NavyNhok said in Performance Issues with Starship – Sporadic FPS Drops:
@Black-Square Hello, The actual version is V0.1.1 ?
Yes.
-
Thank you. That video showed exactly what I was looking for. Notice how the every-other-frame stutter is in the "manipulators" thread? We don't have any documentation on what this actually includes, but it's not usually anything I affect as a developer. I have brought this strange behavior to Asobo's attention, but they have shown no interest yet.
You can read about others encounters with this in v1.0 (I thought it was solved for 1.1, as nobody else has reported it again) here, and a BIOS setting that might have an important impact on this issue. If you try it, please let me know if it makes a difference for you!
In the meantime, I will investigate what systems are connected only to the pilot's avionics switch (more complicated than it sounds with how I've programmed Starship's avionics), and I might give you some more things to try, if you were willing. Thank you!
-
@NavyNhok said in Performance Issues with Starship – Sporadic FPS Drops:
@Black-Square Hello, The actual version is V0.1.1 ?
Yes.
-
I was just testing this a little, and I realized there is something you could try that would be immensely helpful. Sorry to ask for help, but it's very hard troubleshooting something that you can't reproduce on any computer you have access to, as you might imagine.
Next time you see this happening, could you try pulling the following circuit breakers, in this order, and see which one has an effect on the problem?
- RADAR
- ND No. 1
- PFD No. 1
- CDU No. 1
- HF
- ASI No. 1
- ALT No. 1
- SDU No. 2
- ADC No. 1
- Clock PLT
~Only proceed to these, if none of the above made a difference~ - DME No. 1
- FCS No. 1
- FMS No. 1
- ADF
- RAD ALT
- ATC No. 1
- NAV No. 1
Finally, if none of those made a difference, turn off the pilot's avionics switch for one final test.
That should really help narrow things down. I know that might seem like a lot of work, but hopefully it will go very quickly. Ironically, it's also not dissimilar from what a real aircraft might be asked to do by his maintenance technician to troubleshoot the real aircraft.
-
I was just testing this a little, and I realized there is something you could try that would be immensely helpful. Sorry to ask for help, but it's very hard troubleshooting something that you can't reproduce on any computer you have access to, as you might imagine.
Next time you see this happening, could you try pulling the following circuit breakers, in this order, and see which one has an effect on the problem?
- RADAR
- ND No. 1
- PFD No. 1
- CDU No. 1
- HF
- ASI No. 1
- ALT No. 1
- SDU No. 2
- ADC No. 1
- Clock PLT
~Only proceed to these, if none of the above made a difference~ - DME No. 1
- FCS No. 1
- FMS No. 1
- ADF
- RAD ALT
- ATC No. 1
- NAV No. 1
Finally, if none of those made a difference, turn off the pilot's avionics switch for one final test.
That should really help narrow things down. I know that might seem like a lot of work, but hopefully it will go very quickly. Ironically, it's also not dissimilar from what a real aircraft might be asked to do by his maintenance technician to troubleshoot the real aircraft.
-
The BIOS pic has me wondering: the people with FPS issues, could there be thermal throttling at play? My newest build has a 14th gen i9, and for those who follow tech is the Intel cpu that was famously self-destructing on launch. I came in late, but had some issues with stability that were resulting in my CPU asking for (and getting!) upwards of 500A.
I have since become keenly aware of CPU voltages and temperatures lol, but with some BIOS configuration it's been drastically reduced.
-
@Black-Square Sure, as soon as it happens again, I'll check it like you asked.
One question. You listed FCS No. 1 twice. What should the second one be instead of FCS No. 1
And below is a screenshot from my BIOS.
@rafgath Sorry, FMS No. 1.
-
@rafgath Sorry, FMS No. 1.
@Black-Square Another flight and another FPS drop (maybe because it's exactly the same flight every time). Please see the video link below. Luckily, I didn't have to click too many circuit breakers, as everything returned to normal after turning ND No. 1 off and back on.
https://youtu.be/4aDTWlVdmPM
-
Very interesting! That's admitted a little strange, since ND 2 runs the exact same code... This might take a little more experimentation. I will look through things later and see what I can come up with, but on your next flight, try configuring ND 2 to show exactly the same as what ND 1 is showing, and see if the problem is exhibited by both units. Thank you for the help!
-
Very interesting! That's admitted a little strange, since ND 2 runs the exact same code... This might take a little more experimentation. I will look through things later and see what I can come up with, but on your next flight, try configuring ND 2 to show exactly the same as what ND 1 is showing, and see if the problem is exhibited by both units. Thank you for the help!
@Black-Square Okay, I'm uploading another video showing the FPS drop. As you can see, only disabling ND No. 1 helped. Turning it back on doesn’t cause the drop either. But if we look at all three videos I uploaded, they’re all from the same route, and the issue generally always occurs around the same point — just before reaching the ROGAL point. Maybe it’s a coincidence, maybe not.
https://youtu.be/mEYfGcpgg50
