• There seems to be an up tick in Political commentary in recent months. Those of us who are long time members of the site we know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religiours commentary out of the fourms.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politicion will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment amoung members. It is a poison to the community. We apprciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Can anybody help?

Stan V.

Charter Member
:mix-smi:Am having a 'minor' problem with fsx. As fsx is loading, I consistently get a pop up diagnostic very shortly after the music starts playing and before fsx's main menu screen ... It says "Attempt to access a nil value... Stack trace back." No other information is provided. I know exactly what causes this in terms of software execution (trying to jump to a zero instruction or address) but not the circumstances behind it. Obviously I have corruption somewhere in either the data or code. Is there a log file that may point more succinctly to the affected part?

If I simply acknowledge the error, fsx works normally for the rest of my flight which is why I termed it a "minor problem".
 
It could be caused by an addon and not FSX. For example, when FSX starts it will load the aircraft used in your default flight and if there is an error in one of the gauges of that aircraft it may be the cause of the error. Not to mention any addon .dlls that load when FSX starts up (eg Instant Scenery).

Debug by trying to set your default flight to use the default C172.
 
Back
Top