SDK Question Access violation writing location 0xf96f671c.

[JMW]

Getting this message trying to debug.

Unhandled exception at 0x0ea488b7 in orbiter.exe: 0xC0000005: Access violation writing location 0xf96f671c.

Any ideas guys?

Thanks

JMW

 

[agentgonzo]

Post the code you are trying to debug at the point where the access violation occurs

 

[orb]

The instruction at 0x0ea488b7 address is outside of Orbiter.exe. It's most likely located in a module loaded by Orbiter. The access violation could be caused by a bad pointer to some structure.

If you run Orbiter in debugger it should stop just after: the line/function causing this exception, if you are in source code view, or just after the instruction which caused the exception, if there is no source available (not your module or your module built without debug information) and you view disassembly of that part of code.

 

[JMW]

Attached pics of trouble. (it's all Greek to me!) :tiphat:

 

[orb]

Looks like Spacecraft2 vessel is causing this exception. You need to check every vessel defined as Spacecraft2 in the scenario you are running to find the source of this error.

 

[JMW]

Right on the nail (as usual) Orb,
it was UH-1C helicopter (Spacecraft2 vessel)

Hopefully, I'm getting the message - think before you post. (You did say it would be a module) I didn't think of the scenario:facepalm:, only the LaunchPad:thumbup:

Thanks again.

 

[orb]

(You did say it would be a module) I didn't think of the scenario:facepalm:, only the LaunchPad:thumbup:

Thanks again.

Scenarios are containing references to vessel configuration files, which are holding references to vessel modules, so no, I didn't mean a module that is a plug-in, but a generic module, which can be a plug-in, vessel, planet, etc.

You're welcome. :tiphat: