RagnarDa

recent patch and unable to get the module active Please post in the general section of DCS. This is either a) a problem with something on your system denying access to the files (i e antivirus) or b) a installer problem or c) something with the integrity check. Neither of these are made by HeatBlur so we can’t help you beyond the suggestion to try to remove ALL antivirus software and reinstall DCS. Edit: another suggestion is to do a complete anti-virus scan on your computer

Please post your DCS.log. It’s in your saved games folder and DCS world/logs

Any antivirus software running? They sometimes block access to the module dlls.

I would try either trying different settings and see if it goes away, or PM our texture artist ensamvarg to see if the has any ideas. I would also suggest asking in the general DCS section since even though it happens in the Viggen we don’t make the graphics engine and only the model and it might be something with how the cockpit is drawed in the engine.

What happens if you change the resolution?

Thanks! Unfortunately neither that log file contains a Viggen flight. Totally understandable you dont want to try it again. Are you per chance running a overclock? From your desciption it sounds like maybe a over-temperature issue triggered by some infinite loop in Viggen code. What about RAM?

From the log it looks like its a seperate issue, and one I thought I solved or guarded against.

Thanks too, but the log is from a flight of JF-17 and MiG-21 unfortunately and not a Viggen flight :(

Thanks for the report but according to the log the crash is in the menu UI system or Lua hence not in Viggen. Could you maybe post this bug report in the DCS World section?

Can you give me the dcs.log? If you started DCS again it’s saved as DCS.old or something IIRC.

How much RAM do you have? "bad allocation" means out of memory. Memory pieces count is number of times the RWR has received a signal during the mission and it was recorded to memory, and 1826 is quite high (about average one beep every two second for an whole hour). And from Snappys description it sounds also likely that, due to the long mission, there was a lot of data to analyze. I am going to lower the max cap of data to record during a mission and also if the analysis fails for whatever reason it will reset the data and not try to analyze it again.

Are you able to start and quit the game (R and Q)? What keyboard are you using? What language? Any keyboard emulators (ie JoyToJey or HOTAS software) running or anything else that might interfere?

Issue was that the fuzing logic compared the distance between the missiles position over ground and the targets position over sea level. I am uploading a new build now, so the fix will be in next patch of DCS. There seems to be something else about the fuzing not working at some times I think, it sometimes doesnt explode even if it tries to do it. Edit: Thanks for the help guys tracking it down!

Found the problem.

Aaaaaah!

Could you maybe upload the mission you use? Thanks for the help btw.

I don't understand what is going on??? Could you maybe try my test-mission? Edit: and unfortunately neither log nor track provided any clue. The track showed the missile miss by a mil and the log didnt show any targets in close proximity except the ground at one point. Rb05training3.miz

Also please post dcs.log of any failed proximity fuze run.

This is very strange. It works for me??? Can you upload a track file where it consistently (even in the track) flies close to the target?

[emoji46] what about MARK mode?

What happens if you try with a smaller target, like a fighter aircraft?

Hone your skills in hitting enemy targets with the Robot 05 radio-controlled missile! This game will let you practice hitting ground targets while zooming across the terrain in your Viggen with breathtaking 640x480 resolution graphics and COOL music. Can you beat level 11? Find out in this explosive fast-paced computer game. SYSTEM REQUIREMENTS - At least 486 PC but preferably a Pentium. - At least 20 megabytes of RAM but preferably more than 32 megabytes. - A VGA compatible display and graphics card. - A keyboard. No mouse required. - For Windows version: MS Windows 95 or newer. Will NOT work with MS Windows 3.11 or DOS. INSTRUCTIONS - Up key: steer missile upwards. - Down key: steer missile downwards. - Left key: steer missile to the left. - Right key: steer missile to the right. - Alternatively you can use W A S D keys to steer. - R key: start or restart game. - Q key: quit game and return to the operating system. DOWNLOAD ->DOWNLOAD WINDOWS VERSION<- ->DOWNLOAD MACINTOSH VERSION<- ->DOWNLOAD LINUX VERSION<- ->DOWNLOAD RASPBERRYPI VERSION<-

Probable bug found! I had at one point somehow messed up a loop that would run over already analyzed and matched signals in a exponentianl fashion. Another bug was found earlier that would put the area estimation off. I'll have to test some more and upload to ED if it looks OK and we'll likely see the fix in next patch. Thanks for your patience guys!

I am sorry about this. Currently trying to fix this. Meanwhile I suggest don’t switch to BER after landing. The reason IRL you do it is to extend the life of the HUD-light IIRC but I’ve talked to the crew chief and he won’t be mad if you ignore this at this time.