RagnarDa

Ah! I see! Will test again... Thanks!

Hi! So I tried the mission and couldnt replicate the issue. Could you tell me steps to reproduce the issue?

Landing Nav Issues Hi! Thanks for the excellent report and all the others. I’ve had a hard time keeping up to all your new posts but will look into the other issues eventually. This particular issue you describe here is already resolved since I’ve been working with the land nav system the past few weeks. There where multiple issues, as for example north facing runways not working, the switch from turn command to guiding on the approach path not happening when it should as well as the turn command not being centered around the VVI as it should. Thanks for all the help, really appreciate it! <3

Its a ground collision warning. It uses the radar which is pointing forwards to measure if you are about to hit the ground and warns you so you have time to pull up. Also happens when you have a missile in front of the aircraft which is detected by the radar.

I've fixed the issue. Was very simple because of addde's bug report!

I’ve implemented it now. Need to test it so we’ll see when it makes it to public version.

After the Tomcat? Maybe it’ll be a C-2?

Can you send me the mission you experience this in?

Btw I assume you have the landing gears out? Can’t tell by the picture.

This looks like a bug. Is this after you previously flown a mission without shutting down DCS? There are some issues with DCS Viggen not resetting the computer RAM after you spawn a new aircraft and stuff from the previous flight (position of switches, state of avionics etc) is preserved in the new spawn. I have been working on this for a while now and if we are in luck this particular issue might’ve already been fixed.

2-stage Trigger Hi MBot! The toggle variant you are describing is different to the one that is on the Warthog throttle which was the intended use for the provided button binding (the speed brake, boat switch or china hat). Yours is neutral unpressed and the warthogs is neutral when in middle stage. I don’t want to clutter the user interface with all kind of different variants (there would be four different variants for each switch which would be confusing). If you really don’t mind changing three lines in Lua (I do know that you are a scripting wizard) then replace the relevant lines with these: {down = 3005, cockpit_device_id = devices.NAVIGATIONPANEL, value_down = 1.0, value_up = 1.0, name = "T0 Fix (three position switch)", category = "Radar"}, {down = 3006, up = 3005, cockpit_device_id = devices.NAVIGATIONPANEL, value_down = 1.0, value_up = 1.0, name = "T1 Fix (Three position switch)", category = "Radar"}, {down = 3007, up = 3005, cockpit_device_id = devices.NAVIGATIONPANEL, value_down = 1.0, value_up = 1.0, name = "TV Fix (Three position switch)", category = "Radar"}, You only need to map T1 and TV (half press and full press respectively) Edit: After some thinking I realize we might get away with only adding one additional mapping option just for two-stage triggers as the half-press state will probably be activated when moving from fully pressed to fully released. It would look like this: {down = 3006, up = 3005, cockpit_device_id = devices.NAVIGATIONPANEL, value_down = 1.0, value_up = 1.0, name = "T1 Fix (For two-stage trigger)", category = "Radar"}, If you’d like to try it and report back to me I’d add it to the official bindings.

Do you have a dcs.log from one of those times it crashed?

Yeah I am sorry you are having issues. Hopefully we can solve it!

Hi! I had a look at the code and hopefully fixed the issue. I can't test it because the parts for my new PC isn't coming until tomorrow. Thanks for the report!

Yes it is a limitation with DCS at the moment. ED is working on a solution.

Hi! I am investigating but after checking very quickly it looks like seperate issues from the logs. One thing I noticed is that it complains about missing files, an error I don't think I've seen before, so you might want to follow Devrims advice.

Working on AJS-37 Profile for DCS-BIOS I am unfamiliar with DCS BIOS but are you asking for the argument numbers for the individual lights on the caution-panel (errorpanel)??? Edit: if so here they are Left indicator table 406Brand 1 407Brand 2 408BRÄ UPPF 409X-TANK BRÄ 410Tank Pump 411Landställ 412Förv förbj 413Nosställ 414Vställ 415H-ställ 416Tippväxel 417Elfel 418Reserveff 419Hydra-TA 2 420HYDRA TA-1 421AFK FEL 422EJ REV 423OLJETRYCK Right indicator table 424SPAK 425Håll funk 426RHM fel 427Rollväxel 428CK 429Kabinhöjd 430huv o Stol 431TÄNDSYST 432STARTSYST 433MAN BG REG 434SYRGAS 435BRÄ 24 436BRAND GTS 448TILS 438NAV SYST 439KB-V SLUT 440KB-H / KA SL 441FACKL SL 442MOTVERK 443LUFTBROMS

Hey this is OT but since there are often quite a bit of general misunderstanding of how EFMs work in DCS I encourage everyone interested to check out the source code of CptSmileys F-16 or the accompanying NASA papers: https://r.tapatalk.com/shareLink?share_fid=74365&share_tid=95985&url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Fshowthread%2Ephp%3Ft%3D95985&share_type=t

I am pretty sure those nice pictures and detailed text will be included in the updated manual ;) (JediTeo is the author of the DCS:Viggen manual)

Yeah I currently have 500+ unit tests that needs to pass for a release, most of them is for the flight model as thats the most tricky part of the whole module. Code breaks in the most unexpected ways though, like that time when StarForce stopped some functions within the module from being executed (the unit tests, as well as most manual testing was run before SF was applied). A lot of manual testing is needed though, which myself and our QA-team lead by our QA-lead JediTeo takes care of + EDs testers. Issues will get through though, and more likely with features few people use (if the gear handle stopped working we'd noticed a lot sooner).

The targets need to be in a line in depth from the point of view of the missile. A little picture to llustrate (M is missile and <000> is targets). The missile is coming from the left. Correct: --M-> <000> <000> <000> Not correct (will miss): <000> --M-> <000> <000>

Yeah you wouldn't believe how much regressions happen.

Hi! All features of the reconnaissance suit in Viggen was fully implemented years ago. I haven't tested it for a long time so possibly something has broke since then. Sorry for late response and the issue.

Wow! Excellent bug report!

Argh! I've fixed this issue at least once every six months since start of Viggen development. No idea why it keeps cropping up. Can you tell me how your plane was oriented when you experienced the problem (north/east/south/west) and how you read the IAS (in cockpit or external view?)