Jump to content

CTD when trying to change cartridge on Nevada


Mezelf

Recommended Posts

I'm able to guarantee a crash to desktop on the Nevada map whenever I try to change data cartridge with LCTRL+LALT+C. At first I thought putting Marks on the F10 map caused this, but I tried it without putting Marks and it crashed just the same.

 

It's fine on Caucasus.

Haven't tested on PG or Normandy.

Link to comment
Share on other sites

I'm able to guarantee a crash to desktop on the Nevada map whenever I try to change data cartridge with LCTRL+LALT+C. At first I thought putting Marks on the F10 map caused this, but I tried it without putting Marks and it crashed just the same.

 

It's fine on Caucasus.

Haven't tested on PG or Normandy.

 

Can confirm this.

Mission editor, AJS-37 on Nevada Tonapah mil base, no other units on the map.

Having the kneeboard opened and switching through the cardridges with LALT+LCTRL+C and approaching cardridge 6 (coming from 7) makes my DCS OpenBeta 2.5.5.35461 crash.

When switching from 0 to 1 using LSHIFT+LCTRL+C it crashes immediately.

 

Cleaning of folder DCS_AJS37 in Saved Games didn't help!

 

 

Problem Event Name: APPCRASH

Application Name: DCS.exe

Application Version: 2.5.5.35461

Application Timestamp: 5d6eb7db

Fault Module Name: DCS.exe

Fault Module Version: 2.5.5.35461

Fault Module Timestamp: 5d6eb7db

Exception Code: c0000005

Exception Offset: 000000000054489f

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 3079

Additional Information 1: 42b5

Additional Information 2: 42b56f7e0741adc7cde27481ce905bb9

Additional Information 3: d245

Additional Information 4: d245f8153809fe15812a9fb4f59e2fcf


Edited by TOViper

Visit https://www.viggen.training
...Viggen... what more can you ask for?

my computer:
AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TPR | Rift CV1

 

Link to comment
Share on other sites

I tried this and could reproduce this too.

 

Attached is a picture from a popup window while DCS crashed and the last DCS Log file, hope it helps @RagnarDa

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

CTD when trying to change cartridge on Nevada

 

Mezelf or unknown do you have any enemy ground units in the mission?

 

Edit: what happens if you press ”ignore”?


Edited by RagnarDa

DCS AJS37 HACKERMAN

 

There will always be bugs. If everything is a priority nothing is.

Link to comment
Share on other sites

Mezelf or unknown do you have any enemy ground units in the mission?

 

Edit: what happens if you press ”ignore”?

 

Hi RagnarDa,

no ground units at all, just put the viggen on the airfiled/ramp open the kneeboard and switch cartridges, nothing else. I run the latest OB, no mods installed.

 

If i click ignore the popup window appears again, total of 3 times, same message. EDIT: The first time i tried to ignore this i was still in the sim and after the 3rd ignore DCS was still running and i could continue to play/switch cartridge until the next error occured. Like TOViper said:

Having the kneeboard opened and switching through the cardridges with LALT+LCTRL+C and approaching cardridge 6 (coming from 7) makes my DCS OpenBeta 2.5.5.35461 crash.

When switching from 0 to 1 using LSHIFT+LCTRL+C it crashes immediately.

But this worked only the first time, after that DCS will hang after the 3rd ignore and i have kill it with the task manager.

If i click cancel or retray the popup window and DCS close.

 

Edit2: Attached are the new logs (.crash .dmp .log .log.old)

 

Last entries from the Log:

2019-09-28 09:54:29.368 INFO    EDCORE: signal caught: 'Abnormal termination'
2019-09-28 09:54:29.368 INFO    EDCORE: try to write dump information
2019-09-28 09:54:29.369 INFO    EDCORE: # -------------- 20190928-095429 --------------
2019-09-28 09:54:29.370 INFO    EDCORE: DCS/2.5.5.35461 (x86_64; Windows NT 10.0.18362)
2019-09-28 09:54:29.371 INFO    EDCORE: 
2019-09-28 09:54:29.372 INFO    EDCORE: # 00000000 STATUS_SUCCESS

at 00000000 00:00000000
2019-09-28 09:54:29.373 INFO    EDCORE: SymInit: Symbol-SearchPath: '.', symOptions: 534, UserName: 'user'
2019-09-28 09:54:29.374 INFO    EDCORE: OS-Version: 10.0.18362 () 0x100-0x1
2019-09-28 09:54:29.398 INFO    EDCORE: 0x000000000000AD78 (edCore): ed::Random::genInt + 0x14D8
2019-09-28 09:54:29.399 INFO    EDCORE: 0x000000000000C837 (edCore): ed::core::InitBackTrace::InitBackTrace + 0x207
2019-09-28 09:54:29.401 INFO    EDCORE: 0x000000000000CADE (edCore): ed::core::InitBackTrace::InitBackTrace + 0x4AE
2019-09-28 09:54:29.402 INFO    EDCORE: 0x000000000006C31D (ucrtbase): raise + 0x1DD
2019-09-28 09:54:29.405 INFO    EDCORE: 0x000000000006E24A (ucrtbase): get_wpgmptr + 0xE5A
2019-09-28 09:54:29.405 INFO    EDCORE: 0xFFFF800216ED65F8 ((module-name not available)): (function-name not available) + 0x0
2019-09-28 09:54:29.405 INFO    EDCORE: 0xFFFF800216935020 ((module-name not available)): (function-name not available) + 0x0
2019-09-28 09:54:29.405 INFO    EDCORE: 0xFFFF8001F031E020 ((module-name not available)): (function-name not available) + 0x0
2019-09-28 09:54:29.405 INFO    EDCORE: 0xFFFF800216935020 ((module-name not available)): (function-name not available) + 0x0
2019-09-28 09:54:29.579 INFO    EDCORE: Minidump created.

 

and from the log.old

2019-09-28 09:52:35.163 ERROR_ONCE DX11BACKEND: texture 'hb_viggen_ext_rat' not found. Asked from 'NGMODEL'
2019-09-28 09:52:35.163 ERROR_ONCE DX11BACKEND: texture 'hb_viggen_ext_rat_nrm' not found. Asked from 'NGMODEL'
2019-09-28 09:52:46.373 INFO    VIGGEN: Found 9 .ini files in SavedGames/DCS_AJS37
2019-09-28 09:52:46.373 INFO    VIGGEN: FOLDERID_SavedGames: C:\Users\user\Saved Games
2019-09-28 09:52:46.373 INFO    VIGGEN: Custom cartridge file found! C:\Users\user\Saved Games\DCS_AJS37\Autogenerated 1.ini
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 0d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 WARNING LOG: 3 duplicate message(s) skipped.
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 42.0389d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 WARNING LOG: 5 duplicate message(s) skipped.
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 0d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 42.0683d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 WARNING LOG: 5 duplicate message(s) skipped.
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 0d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 41.9057d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 WARNING LOG: 5 duplicate message(s) skipped.
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 0d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 41.664d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 WARNING LOG: 5 duplicate message(s) skipped.
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 0d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 41.8272d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 WARNING LOG: 5 duplicate message(s) skipped.
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 0d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 41.9896d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 WARNING LOG: 5 duplicate message(s) skipped.
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 0d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 42.0389d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 WARNING LOG: 5 duplicate message(s) skipped.
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 0d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 41.7849d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 WARNING LOG: 5 duplicate message(s) skipped.
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 0d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 ERROR   EDTERRAINCORE: utm_private::fromLatLon Longitude 41.7849d more than 60d from center of UTM zone 11
2019-09-28 09:52:46.373 WARNING LOG: 5 duplicate message(s) skipped.


Edited by unknown

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

What happens if you place a enemy unit in the mission? Thanks for helping me narrowing it down btw!

It still crashes, 1 friendly unit, or 1 enemy unit or both, ground/air. No difference if you try to change the cartridge cold on the ramp, hot on the runway or hot in the air, without or with markpoints on the F10 map.

Like Mezelf said, this only happens on the Nevada map, the 3 other maps are fine

 

EDIT: Thank you for looking at this on a weekend! :beer:


Edited by unknown

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Nevada is the only map with a 3 digit longitude. The first digit is omitted by the DCS Viggen as a workaround afaik.

 

Could it have something to do with this? Just a shot in the dark...

Specs:

 

 

i9 10900K @ 5.1 GHz, EVGA GTX 1080Ti, MSI Z490 MEG Godlike, 32GB DDR4 @ 3600, Win 10, Samsung S34E790C, Vive, TIR5, 10cm extended Warthog on WarBRD, Crosswinds

 

Link to comment
Share on other sites

Guys, I am not able to reproduce the crash. I tried:

 

1. Running Cold start up in Nevada quick mission

2. Custom empty mission whit hot start from runway

3. Added enemy radar emitters (russian awacs and TOR) and set to BER-mode (so a ELINT-analysis is performed)

4. Deleted DCS_AJS37 folder in Saved games and tried a new empty mission

5. Added F10 markers

 

All in single-player and changed cartridges at every step. Anything else I should try?

 

Anyway, I'll do the pragmatic thing and disable the assertion so the game won't crash and instead show and error in dcs.log

 

Nevada is the only map with a 3 digit longitude. The first digit is omitted by the DCS Viggen as a workaround afaik.

 

Could it have something to do with this? Just a shot in the dark...

Most likely, judging from the warnings in unknowns log. It's also the issue with longitude being westward and probably then negative.

 

EDIT: Thank you for looking at this on a weekend! :beer:

We kind of try to give the opposite impression, but developing for DCS isn't any of ours day job. If I'd hoped to try to support myself on module-development I'd make quite a lot of other choices :D

DCS AJS37 HACKERMAN

 

There will always be bugs. If everything is a priority nothing is.

Link to comment
Share on other sites

Oh and one final idea: have any of you used any third party cartridge generating tool?

 

Try opening the file c:/Program files/Eagle Dynamics/DCS World/mods/aircraft/AJS37/Cockpit/scripts/Navigationpanel/Device/init.lua

 

and delete everything between line 303 to 377, so from the line under this:

Data_cartridges = {

 

to the line above this:

}

 

and by that removing all cartridges in the old data-cartridge system which is deprecated and should probably be removed altogether.

DCS AJS37 HACKERMAN

 

There will always be bugs. If everything is a priority nothing is.

Link to comment
Share on other sites

Oh and one final idea: have any of you used any third party cartridge generating tool?

 

Try opening the file c:/Program files/Eagle Dynamics/DCS World/mods/aircraft/AJS37/Cockpit/scripts/Navigationpanel/Device/init.lua

 

and delete everything between line 303 to 377, so from the line under this:

Data_cartridges = {

 

to the line above this:

}

 

and by that removing all cartridges in the old data-cartridge system which is deprecated and should probably be removed altogether.

Hi RagnarDa,

i used a tool a while ago where you could generate custom cartridges.

 

Anyway, the bold text of your last post was the FIX on my end!

 

I don't know if this is of any interest/help for you, i post the deleted part of the lua file here:

 

{
	cartridgenr = 1, -- Can be 1 to 5
	waypointnr = 0, -- From 0 to 10 where 0 i starting base LS and 10 is L1. Nearest pre-programmed airbase will be used.
	latitude = 41.60917, -- Degrees
	latitudeminutes = 0, -- Optional
	latitudeseconds = 0, -- Optional
	longitude = 41.60028, -- Degrees
	longitudeminutes = 0, -- Optional
	longitudeseconds = 0, -- Optional
	missiontime = 0, -- Optional. ETA in seconds from the start of the mission or when the aircraft is spawned.
	velocity = 0, -- Optional. Sets a forced speed in m/s.
	etalocked = false, -- Set to true to make the waypoint use the missiontime. Waypoint will be converted to targetpoint (Målpunkt)
	velocitylocked = false, -- Set to true to use the forced speed.
	istargetpoint = false, -- Set to true to set the waypoint as a targetpoint.
},
{
	cartridgenr = 1, -- Can be 1 to 5
	waypointnr = 1, -- From 0 to 10 where 0 i starting base LS and 10 is L1. Nearest pre-programmed airbase will be used.
	latitude = 41.93028, -- Degrees
	latitudeminutes = 0, -- Optional
	latitudeseconds = 0, -- Optional
	longitude = 41.86528, -- Degrees
	longitudeminutes = 0, -- Optional
	longitudeseconds = 0, -- Optional
	missiontime = 0, -- Optional. ETA in seconds from the start of the mission or when the aircraft is spawned.
	velocity = 0, -- Optional. Sets a forced speed in m/s.
	etalocked = false, -- Set to true to make the waypoint use the missiontime. Waypoint will be converted to targetpoint (Målpunkt)
	velocitylocked = false, -- Set to true to use the forced speed.
	istargetpoint = false, -- Set to true to set the waypoint as a targetpoint.
},
{
	cartridgenr = 1, -- Can be 1 to 5
	waypointnr = 2, -- From 0 to 10 where 0 i starting base LS and 10 is L1. Nearest pre-programmed airbase will be used.
	latitude = 42, -- Degrees
	latitudeminutes = 0, -- Optional
	latitudeseconds = 0, -- Optional
	longitude = 42, -- Degrees
	longitudeminutes = 0, -- Optional
	longitudeseconds = 0, -- Optional
	missiontime = 0, -- Optional. ETA in seconds from the start of the mission or when the aircraft is spawned.
	velocity = 340*0.8, -- Optional. Sets a forced speed in m/s.
	etalocked = false, -- Set to true to make the waypoint use the missiontime. Waypoint will be converted to targetpoint (Målpunkt)
	velocitylocked = true, -- Set to true to use the forced speed.
	istargetpoint = false, -- Set to true to set the waypoint as a targetpoint.
},
{
	cartridgenr = 1, -- Can be 1 to 5
	waypointnr = 3, -- From 0 to 10 where 0 i starting base LS and 10 is L1. Nearest pre-programmed airbase will be used.
	latitude = 42, -- Degrees
	latitudeminutes = 55, -- Optional
	latitudeseconds = 55, -- Optional
	longitude = 42, -- Degrees
	longitudeminutes = 55, -- Optional
	longitudeseconds = 55, -- Optional
	missiontime = 0, -- Optional. ETA in seconds from the start of the mission or when the aircraft is spawned.
	velocity = 0, -- Optional. Sets a forced speed in m/s.
	etalocked = false, -- Set to true to make the waypoint use the missiontime. Waypoint will be converted to targetpoint (Målpunkt)
	velocitylocked = false, -- Set to true to use the forced speed.
	istargetpoint = false, -- Set to true to set the waypoint as a targetpoint.
},
{
	cartridgenr = 1, -- Can be 1 to 5
	waypointnr = 10, -- From 0 to 10 where 0 i starting base LS and 10 is L1. Nearest pre-programmed airbase will be used.
	latitude = 42.17750, -- Degrees
	latitudeminutes = 0, -- Optional
	latitudeseconds = 0, -- Optional
	longitude = 42.48194, -- Degrees
	longitudeminutes = 0, -- Optional
	longitudeseconds = 0, -- Optional
	missiontime = 0, -- Optional. ETA in seconds from the start of the mission or when the aircraft is spawned.
	velocity = 0, -- Optional. Sets a forced speed in m/s.
	etalocked = false, -- Set to true to make the waypoint use the missiontime. Waypoint will be converted to targetpoint (Målpunkt)
	velocitylocked = false, -- Set to true to use the forced speed.
	istargetpoint = false, -- Set to true to set the waypoint as a targetpoint.
},

 

Thank you very much for the quick help, i hope this will fix the problem for the other guys too.


Edited by unknown

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Oh and one final idea: have any of you used any third party cartridge generating tool?

 

Try opening the file c:/Program files/Eagle Dynamics/DCS World/mods/aircraft/AJS37/Cockpit/scripts/Navigationpanel/Device/init.lua

 

and delete everything between line 303 to 377, so from the line under this:

Data_cartridges = {

 

to the line above this:

}

 

and by that removing all cartridges in the old data-cartridge system which is deprecated and should probably be removed altogether.

 

 

This fixed it for me as well, thank you!

Link to comment
Share on other sites

  • Recently Browsing   0 members

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