Jump to content

Recommended Posts

Posted

Hi! I've encountered a problem with my custom flight model.
Every time I try to eject, or the pilot dies, DCS crashes and I have to forcefully close it. When this happens, the last 4 lines of the log file are: 

2023-07-10 15:17:12.315 INFO    APP (Main): invalid input at index 0 in ed_fm_add_local_force
2023-07-10 15:17:12.315 INFO    APP (Main): invalid input at index 0 in ed_fm_add_local_moment
2023-07-10 15:17:12.325 INFO    APP (Main): invalid input at index 0 in ed_fm_add_local_force
2023-07-10 15:17:12.325 INFO    APP (Main): invalid input at index 0 in ed_fm_add_local_moment
2023-07-10 15:17:12.325 INFO    APP (Main): invalid input at index 0 in ed_fm_add_local_force
2023-07-10 15:17:12.325 INFO    APP (Main): invalid input at index 0 in ed_fm_add_local_moment

When the source code is identical to the template, I get to collect additional crash info. This is the .crash file:

2023-07-10 15:08:40.046 INFO    EDCORE (Main): # -------------- 20230710-150840 --------------
2023-07-10 15:08:40.046 INFO    EDCORE (Main): DCS/2.8.4.39731 (x86_64; Windows NT 10.0.19045)
2023-07-10 15:08:40.047 INFO    EDCORE (Main): C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\GraphicsVista.dll
2023-07-10 15:08:40.047 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffdc2650ca8 00:00000000
2023-07-10 15:08:40.048 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin;', symOptions: 532, UserName: ''
2023-07-10 15:08:40.048 INFO    EDCORE (Main): OS-Version: 10.0.19045 () 0x300-0x1
2023-07-10 15:08:40.049 INFO    EDCORE (Main): 0x0000000000040ca8 (GraphicsVista): Graphics::AnimHolder::CURRENT + 0x31D0
2023-07-10 15:08:40.049 INFO    EDCORE (Main): 0x00000000006fd50c (DCS): SW + 0x266D0C
2023-07-10 15:08:40.049 INFO    EDCORE (Main): 0x00000000006d7984 (DCS): SW + 0x241184
2023-07-10 15:08:40.050 INFO    EDCORE (Main): 0x00000000006d7aee (DCS): SW + 0x2412EE
2023-07-10 15:08:40.050 INFO    EDCORE (Main): 0x00000000006a3c38 (DCS): SW + 0x20D438
2023-07-10 15:08:40.050 INFO    EDCORE (Main): 0x0000000000003b53 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x4C3
2023-07-10 15:08:40.050 INFO    EDCORE (Main): 0x000000000000405e (World): wSimCalendar::DoActionsUntil + 0x1FE
2023-07-10 15:08:40.050 INFO    EDCORE (Main): 0x0000000000874898 (DCS): SW + 0x3DE098
2023-07-10 15:08:40.050 INFO    EDCORE (Main): 0x0000000000874561 (DCS): SW + 0x3DDD61
2023-07-10 15:08:40.050 INFO    EDCORE (Main): 0x0000000000895959 (DCS): SW + 0x3FF159
2023-07-10 15:08:40.050 INFO    EDCORE (Main): 0x0000000000853cc4 (DCS): SW + 0x3BD4C4
2023-07-10 15:08:40.051 INFO    EDCORE (Main): 0x0000000000854ba4 (DCS): SW + 0x3BE3A4
2023-07-10 15:08:40.051 INFO    EDCORE (Main): 0x000000000236cb1f (DCS): AmdPowerXpressRequestHighPerformance + 0xFC4B1B
2023-07-10 15:08:40.051 INFO    EDCORE (Main): 0x0000000000c54182 (DCS): SW + 0x7BD982
2023-07-10 15:08:40.051 INFO    EDCORE (Main): 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14

If anyone knows what's going on, I'll greatly appreciate it if you could share your thoughts on how to fix this.
Thanks!

  • 4 weeks later...
Posted

UPDATE:

I discovered that while the "DCS has crashed" error message is up and I try to close DCS itself, the simulation resumes when the "are you sure" prompt shows up. This makes the issue a bit more weird to me.

  • 2 weeks later...
Posted

UPDATE:

After doing a lot more testing, it seems to be linked to the cockpit's main panel.

Leaving out the main panel declaration in the device init file fixes it, but at the expense of breaking all the cockpit panel stuff like gauges and indicators.

Posted

UPDATE:

I discovered something a bit unfortunate. Using FC3 avionics (Su-27, F-15C, Su-25, etc.) combined with a custom flight model AND a custom main panel leads to DCS crashing when the pilot ejects or is killed in the cockpit. My guess is that DCS doesn't know how to handle this, so it crashes. 

This makes aircraft mod creation a lot more difficult because all the avionics, targeting systems, and other stuff from FC3 would need to be done separately like the A-4 mod, but maybe there's a way around this.

Again, the only problem, which is a big one, is that DCS crashes when there's no pilot controlling the aircraft. Everything else works fine.

  • 3 months later...
Posted

UPDATE:

I finally figured out a way around this! 

The solution is to go to the aircraft declaration file and state that there is more than one pilot.

The cockpit sound muffling bight be disabled for some reason, but that can be fixed. Also, the cockpit view and maybe even controls might still work, but that's a minor issue in my opinion compared to DCS crashing.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...