RagnarDa

Do you mind posting your DCS.log after a crash?

I would try a complete reinstall of DCS. Also try posting in the general DCS World forum or Steam forums since this is probably not exactly an issue with the Viggen module but rather the module manager/installer in DCS/Steam.

Did you disable all anti-virus software?

AJS37 CTD https://r.tapatalk.com/shareLink/topic?share_fid=74365&share_tid=274875&url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Fshowthread%2Ephp%3Ft%3D274875&share_type=t&link_source=app

See here AJS37 CTD https://r.tapatalk.com/shareLink/topic?share_fid=74365&share_tid=274875&url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Fshowthread%2Ephp%3Ft%3D274875&share_type=t&link_source=app

AJS37 CTD I have replicated the issue. If you wait long enough the computer will get responsive again (for me it was 5 minutes for a 20 minutes mission, and I wasn’t even kicked off the server I was playing on). I am currently considering the alternatives for solving this issue.

Aww... fact is I made great efforts, for unclear reasons, to sanitize the marker texts but forgot about the filename.

Yes

This issue has been fixed and will be included in next patch. There will be one cartridge per player and you can tell which one has been created by who in the kneeboard so you select either your own or anyone elses flying on your side.

Thanks for the reports and track-files. Turns out there where two problems: one was that there was somehow a hard-coded max distance for detection by the RWR. The other was that there was a blind-spot somehow at 12'o clock on the RWR. I've finally implemented the "overlapping" functionality of the RWR-antennas now so there will be two lights on the RWR on when the emitter is between the coverage of two antennas. This will also help with ELINT-analyzis as the accuracy will improve. Fixes will be in next patch of DCS open beta.

See here: https://forums.eagle.ru/showpost.php?p=4292785&postcount=2 Could you tell me more in detail what you did before it crashed? Is there somewhere I could download the Grim Reapers mission file?

Thanks for reporting! There are now multiple reports of what I believe is the same issue. I have now been able to reproduce a crash when pressing wheels brakes on the runway. Unfortunately the crash isn't in my code, so I've forwarded it to ED. There is a possibly unrelated warning in your dcs.log that I am trying to track down the causes to too (I can't reproduce this). The NaN (Not a Number) is like a virus that originates... from somewhere. I've added more checks related to elevon angles as that is what I can see from your log, but unless I am able to reproduce that, the hunt will continue in next patch if users are able to get the warning and can post it here.

Hi! Sorry that you are having this problem. Could you post the dcs.log after a crash? It's located in C:\Users\yourname\Saved Games\DCS.openbeta\logs

I will upload a fix to ED (a reversal really) in a little while so it will likely be with next patch for DCS. Strange thing is that It Worked On My Machine . EDIT: Files uploaded. Awaiting next DCS build.

Could you maybe post a video? What is blinking? The firing order doesn’t blink, but the timeline blinks 2 seconds prior to firing order.

I mean it is green.... [emoji3] Btw if you turn on English auto generated subtitles on YouTube it does translate Viggen to vegan

Actually no the feature was dropped when we switched to EDs implementation of gliding cluster munitions, but we had it before. I don’t think there is a way to do this within current system and I have asked about it exactly once but it’s not something I will pursue aggressively. It’s a few seconds of flight time before it enters the fixed attack height anyway.

Just FYI: you can select missile 1 by setting IRRB on the weapons-selector on your right side and then either setting master mode ANF or trigger unsafe. Or you could cycle back to missile 1 one by pressing IRRB-FRAMSTEGN (missile step) multiple times.

Thanks for reporting! It's been fixed now.

OK thanks for reporting! Both issues fixed.

Nice! I am on my phone so can’t access it and I don’t know much French unfortunately (except “merde” [emoji3]) but if it looks OK would it be alright if we included it with the official module install?

Thanks for all the reports! I am happy to say that I finally finished implementing and integrating the custom bombing solution that was started in this stream: https://forums.eagle.ru/showthread.php?t=259071 While integrating this I discovered a old bug where the air density (which is supposed to be set by ground crew) was not changed and always had a default value. This would lead to slightly inaccurate airspeed readings. Using the new ballistics calculations I had very accurate results, better than with the old way. I even downloaded a track posted in this thread and even though the description said the bombs fell short when replying it now the bombs went on target. Probably needs a bit more testing but I am quite excited to maybe finally being able to put this issue to rest.

They show different things. If the HUD fin is touching the ring you have the right speed and acceleration to reach the _current waypoint_ on time. You could however currently be very late (but catching up), or early (but flying slower than planned). If the TID-output shows 0 then you are at the planned distance to waypoint at the right time, but it doesn’t say that you will _arrive_ on time. You could be flying too slow or fast. If both time-errors are zero then you are flying at the planned speed.

There is no IFF-system in DCS. Viggen has an old IFF-implementation that has never been finished because its missing animation in cockpit and other modules would need to implement the interrogation signal.

Thanks for reporting! In the meantime: don’t press it (it doesn’t do anything) :D