RagnarDa

:( Could you guys maybe test the same in some other module? We had a crashing bug when Viggen unloaded but that was fixed at least internally a while ago. Neither me nor anyone in the testing-team has had any CTDs since.

If you start the DCS updater the new open beta should contain fix for the Viggen crash.

Before anyone asks: the FRAMSTEGN (missile step) is not functional, it was just added to the bindable controls for keyboard.

When starting on the ground the throttle is set to ground-idle. If not it is a bug. About resetting the controls: the intended behavior in DCS is that it always starts the same way so you don’t need to reset controls. BUT, I unfortunately discovered quite late in the process of coding Viggen that I had to do this manually, so I had to go back and make sure hundreds upon hundreds of variables is properly re-initialized between spawns. It has been difficult to find all so sometimes you might notice like a switch or something being in the same position as your last flight. If you see this, please let me know. There is a very simple mechanism to find the trim implemented but it isn’t working perfectly (just about close enough). In F-14 I believe Swither made it so that the autopilot is on for a few seconds when you spawn, thereby trimming the plane. I’ve considered it for Viggen, just hasn’t come around to trying it out.

Yes it is the same issue

Yes it’s an issue when unloading the Viggen or starting it again that was unfortunately missed. What happened was that I thought I discovered a memory leak and tried to recover some memory when de-spawning but that memory didn’t belong to Viggen but DCS, hence memory access violation. I fixed the code but it apparently wasn’t fast enough to make it into the update of the open beta. Sorry about that :( I think you can still use the stable version of DCS or you can restart DCS between spawns, until the next patch is released. Again, sorry about this and such a shame this is your first impression of something we worked so hard with and are so immensely proud of.

I’ve set the throttle to full mil on spawn now (that’s why you have to move it, I don’t have to move it much though). I’ve changed the trim to 3 degrees default now, will be in next update.

The fix is in, but unsure it will make it to the event

Nice feature but singleplayer only ? The solution I’ve used to implement this is blocked for clients in multiplayer. I’ve asked ED to unblock it but they are not convinced 3rd parties should be able to do this. I hope it will change since Bas90 is such a specific feature for the Viggen (very central to its design even more than carriers ops for F-18). It would also be super helpful debugging in MP-environment.

Fixed! The fixed files are being uploaded to ED right now. Thanks for the reports, good thing it was easy to replicate!

Yeah I answered during lunch-break at work. I wasn’t able to get to the dev-computer last night as the kid wouldn’t fall asleep and today I have other obligations but hopefully might be able to check on Sunday earliest. Thanks for the video! It makes fixing stuff way more easier and faster.

Don’t think there is a missile called RBS-15G (at least I never heard of it)

I believe all of these issues except for RAT “should” work but if you say they don’t it might be bugs introduced. The RAT hasn’t been animated hence not “working” (though I believe it is coded IIRC). Thanks for the list!

I think some of the changes in the list came a little too late to make it into yesterday’s update.

Fixed! Here’s what happened: 1) Upon first implementing this mode I apparently coded so release would be disallowed on L, LS, UP and so on waypoints. Don’t know why, probably brain fart. The code didn’t function though so release was allowed anyway. 2) Running static analysis years later revealed that the disallowing was not functioning so I “fixed” it. 3) Now when overflying a target it would automatically switch to next waypoint since you are in NAV-mode but if the next waypoint was L-waypoint the release was disallowed. Anyway fixed in internal version and will be in next release or the one after that.

Hi everyone! I've fixed the issue now. Thanks for the reports! The reason it took so long is because the issue is of pretty low severity compared to other issues I've been working on like the gun-sight issue. See for example here: https://www.softwaretestinghelp.com/how-to-set-defect-priority-and-severity-with-defect-triage-process/

Fixed! Thanks for the reports!

The cone for U22 and U22/A is modeled. It’s also modeled to have additional chance to break missile guidance radars (CW).

I don’t think so

ELINT Map Information Sharing? The ELINT-data is saved to your Saved Games-folder under DCS_AJS37\ELINTData.info. From this you could either manually or through some app copy the coordinates to \DCS_AJS37\CustomCartridge.ini for loading in the mission. See 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 Edit: Missing in the description is the instruction to select cartridge number 7 to load the one in saved games.

It sounds like at least the barometric altitude is wrong. The target-ring is relative your barometric altitude and it might float above the ground if your barometric altitude is too low or appear under the ground if your barometric altitude is too high. You can adjust to the local pressure by switching the LD/RHM switch on the right side of the front panel to LD and then adjust the pressure on the altimeter so that the radar-altimeter markings (two horizontal lines on the HUD by the outermost vertical lines in NAV-mode) just touches the vertical lines.

Eh, no I don’t think so. Didn’t think about that.

Fixed! Will be in next release. Thanks for the report!

INS broken after newest Open Beta update 11/05/18 Do you have a dcs.log? Look into %SAVEDGAMES%/DCS World OpenBeta/logs - folder.

Thanks guys!