RagnarDa

Also, if you do test it could you upload the dcs.log? Many thanks!

The settings was reversed so you turned ON terrnav by entering 581 and turning it OFF by 580. It is fixed now.

Hey could you test it with an airstart in the air and also try "every frame" FIRST and then try without "every frame" ?

Here’s how to select cartridges: 2018 Kickoff! Development Changelog https://r.tapatalk.com/shareLink?share_fid=74365&share_tid=199206&share_pid=3347736&url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Fshowthread%2Ephp%3Fp%3D3347736&share_type=t

Sorry here’s the instructions for the data-cartridge in Saved-games folder. 2018 Kickoff! Development Changelog https://r.tapatalk.com/shareLink?share_fid=74365&share_tid=199206&share_pid=3346749&url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Fshowthread%2Ephp%3Fp%3D3346749&share_type=t

Press T1 to get the E (nav-update mode). In this mode the waypoint won’t be automatically switched over, nor will it in any other mode than NAV.

Did you use the Rb04 and Rb15 for AI? There are two selectable ones and one is for players other for AI.

Fixes will done for a while on the code-side but not the art since it is less work maintaining two branches on the code and everything is already set up for that. ED however stated that only major issues will be patched on 1.5.8 so it’s not sure the fixes will reach the end-user. Also if it start being too much work with having two branches I’ll have to stop merging into 1.5.8 too.

I wasn’t able to fully correct the sight, but I hope I at least haven’t made it worse...

Yeah bare in mind that it was a couple of years ago I researched and coded this so my memory is probably at fault and I’m at work and can’t check the documentation but I thiiiink I wasn’t able to find the actual trim-control in the cockpit and by that assumed it wasn’t usable by the pilot. Probably wrong though so please correct me. The RENFLYGN control being a gain-control actually makes sense, thanks for that!

Truthfully and IIRC, I am not entirely sure there is a rudder trim in the Viggen except for the emergency one. Also, not sure what the “RENFLYGN” rotary actually does since the RL-manual is very light on information about that.

RB15 Missile programming I’ve seen this issue reported before and haven’t had time to look at it yet. The same settings for Bk90 seems also to not have any effect even though they should which leads me to believe that the issue might be the STD/PREP-switch might be the culprit. Earlier there was an issue that the state of the switch was reversed (prep was acually std and vice versa) but it might be something like it needs to be cycled before it it’s state is read correctly. Will try to take a look as soon as I can.

Help with rockets. Just want to drop in and say that I can confirm that the rockets do consistently fall around 200m short for me too. I’ve spent the better part of last week and the whole weekend trying to figure out what is wrong and even though I did find some bugs (for example radar distance measurement was wrong) I haven’t quite nailed down the core issue. I might have had a break through last night though, eager to get home from work and try it out (after the diaper changes and all [emoji3] ) Thanks for the reports and your patience!

Send them to me or post them here. Sorry you are having issues, hope we can solve it!

I think I fixed that as well yes

Hmm... If you cycle to cartridge nr 7 does the name of the cartridge as specified in CustomCartridge.ini show up? Is there any info in the dcs.log? Sorry if it doesnt work, just got it done days before the 2.2 update and nobody else had time to QA it... :(

Yes

Said and done. Will try to verify if track replay fidelity actually improve. I’ll expect it to not be perfect still as there are probably other issues but maybe 80% improvement...

This is would only work in DCS 2.2 as it is included with Friday’s update. Once you loaded the cartridge it won’t change until you load it again even if you edit the files. It is shown in this video around 1:00min mark how to select and load a different data cartridge:

Yeah the problem is probably because I used std::rand with a new seed for random events instead of using EDs random-generator that would probably provide the same sequence-result in the replay. It’s on my to-do list to change the code.

Did anyone try the auto-generated data cartridge yet? It hasnt been very thoroughly tested but I thought that it wouldnt matter much since if it doesnt work it wouldnt affect the game much anyway. The new way of loading cartridges from a file is file that looks like this: cartridgename = Custom cartridge test [LS] latitude = 41.60917 latitudeminutes = 0 latitudeseconds = 0 longitude = 41.60028 longitudeminutes = 0 longitudeseconds = 0 missiontime = 0 velocity = 0 etalocked = false velocitylocked = false istargetpoint = false [b1] latitude = 41.93028 latitudeminutes = 0 latitudeseconds = 0 longitude = 41.86528 longitudeminutes = 0 longitudeseconds = 0 missiontime = 0 velocity = 0 etalocked = false velocitylocked = false istargetpoint = false [b2] latitude = 42 latitudeminutes = 0 latitudeseconds = 0 longitude = 42 longitudeminutes = 0 longitudeseconds = 0 missiontime = 0 velocity = 272 etalocked = false velocitylocked = true istargetpoint = false [b3] latitude = 42 latitudeminutes = 55 latitudeseconds = 55 longitude = 42 longitudeminutes = 55 longitudeseconds = 55 missiontime = 0 velocity = 0 etalocked = false velocitylocked = false istargetpoint = false [L1] latitude = 42.17750 latitudeminutes = 0 latitudeseconds = 0 longitude = 42.48194 longitudeminutes = 0 longitudeseconds = 0 missiontime = 0 velocity = 0 etalocked = false velocitylocked = false istargetpoint = false The file should be named CustomCartridge.ini and be saved in %SAVEDGAMES%/DCS_AJS37/. The files is loaded every 10 seconds so you dont need to respawn to reload it. The ELINT-export is only exported if the folder %SAVEDGAMES%/DCS_AJS37/ exists and is called ELINTData.info and is the same info you would see in the kneeboard. Both of these files is of course meant to be used with a external planning application.

Hi! I looked at the logs and tried the replay on my computer and unfortunately wasnt able to pinpoint what went wrong nor did I get a crash on my computer... Did you try to update today or yesterday? There was a new version of DCS 2.2 released. Also, try a repair of DCS. Another thing you could test is create a mission with the Viggen in an airstart and see if it works for you. I am sorry you are having issues and hope we can sort it out!

Thanks for the reports! Hopefully fixed the problems. Not sure it will make it into next release but maybe the one after that. The issues was that setting mode F with U22/A would always set it to listening mode, the U22 wouldnt light the MOTVERK-lamp and one of the payloads was named U22/A but contained a U22 which might cause confusion. Also made it preconfigured for whatever pod you carried on a hot start.

Thanks! Decided to spend the weekend at home this year (got a baby this november) so there is a little time to work on the Viggen between diaper changes. Happy New Year to you too!

Fixed! Will probably be in next update. Thanks for the reports!