cannot reproduce Quick Missions on Normandy Map Issue

[Monash]

I recently purchased and installed the new Normandy map.  I previously owned both the Channel and Normandy 1944 maps.

When starting a quick mission with the F-86 on Normandy 2.0 the game always crashes. 

When staring with the Mosquito, the mission starts, but it looks like the old Normandy map.

I have uninstalled and reinstalled the Normandy update and repaired my DCS installation.  I am not using multi-threading.  I have not had this issue in the past.

I suspect these quick missions have not been updated to use the new map, but I just guessing.

Can anyone clarify if this is an general issue with these missions, or if I should be concerned that there is something amiss with my installation.

 

[Art-J]

Verify first if the map installed and activated correctly on your PC. In the mission editor you should be able to mouse-drag to London and Paris regions, with all the extra airbases out there, also, in the mission itself you should see all the buildings in these cities with high resolution textures.

Mosquito Rhubarb mission loaded correctly for me, but I've never played it on the old version of the map, so I don't know how different the graphics was. In some areas old and new map looked similar, in the others the difference is more striking.

As for the F-86 instant missions, I only tried the first, cold start one and indeed, DCS seems to have frozen solid. Have to try again later, see if any crash logs are being generated and then post them here. Without logs, troubleshooting is almost impossible.

Edited April 25, 2023 by Art-J

[Monash]

I believe the map is installed and activated correctly.  It shows up as installed in the module manager.  Selecting the map in the mission editor appears to use the newer map.  At least London and Paris appear on the map in the editor so I assume this means all is good installation-wise. 

I retried the Mosquito Rhubarb instant mission (after uninstalling and reinstalling the map) and now I think the correct version is loading.  The textures look good and I can see London and Paris on the F10 map. 

As you replicated, I continue to get crashes on the F-86 instant missions. I've attached the log files (Instant Mission, F-86, Normandy, Take Off)

I also tried an Instant mission using the MiG15bis.  This time the mission loaded, and London (and perhaps Paris) appear on the F10 map.  However, the map is frozen: I cannot move the map using either the middle or right mouse button, and cannot zoom in or out.  So while it looks like the very northern part Paris appears on the map, I cannot move the map area shown to verify that Paris is really there.  I've attached a screenshot. 

 

 

dcs.log-20230425-120535.zip

Edited April 25, 2023 by Monash

[NineLine]

I have been unable to reproduce the crash with the F-86, please make sure to run a clean up and make sure no mods are being used and let me know, thanks. 

[Art-J]

@NineLine Thanks for taking a look. I think I might have narrowed the culprit in my particular case. It's the Nin's sound mod for MiG-21, not all of it even, only the part that needs to be extracted to Saved Games location.

DCS froze and had to be killed via task manager, so no crash log, but the other files are attached below. Not sure, however, if they'll help in figuring out which file from the mod causes the freeze.

Logs.zip

[Monash]

@NineLine I echo Art-J's thanks for taking a look at this.  I uninstalled the game including the saved game folder and reinstalled.  I only installed the base game + Normandy 2.0 + F-86 module.  This appears to have solved the issue.  I can start the F-86 instant missions on the new map, and the F10 view works as it should.  London and Paris appear on the map.  So I guess there was something wrong with my install, but I can't figure what.  I only had Tacview and DCS SRS installed before and reinstalling them has not caused the issue to reappear.

I'm now going to reinstall all my other modules.  Hopefully that will not break anything, but at the moment it looks like the problem was on my end and reinstalling the game fixed the issue.