RagnarDa

Uh yes. I am unsure how the behavior should be because only 2 Bk90 was actually allowed to be carried in the air force and the documents on the behavior of launching Bk90s only describes carrying two. BUT it could actually carry 4 but wasn’t allowed because some aerodynamic reasons. The modeling of 4 Bk90s is me pretty much approximating how it should work and apparently I thought the light might lit after launching two in series. It might be incorrect and could be changed but there is no telling what behavior actually would be correct.

Just a quick response without checking the documents but IIRC the attack altitude is always 60m. The approach altitude otoh can be set with TAKT.

We think it is a bug in DCS where the weight-on-wheel data didn’t work (the reverser only engages when nose wheel is on the ground). ED is notified and they think they located the problem. We just created a workaround to get weight one wheel status in another way.

Ah sorry you are correct. Wrote from memory

What are the details around these new data cartridges in the beta update? You can either use the already generated mission for the closest enemy unit or you can create a MÅL point by setting SPA-mode and RefLola and Out then inputting target coordinates, and then L/MÅL and a number on the _keypad_ (Not B1-B9). Then set master mode to BER and select the generated cartridge as described above. Edit: _VIND/RUTA MÅL_ not REFLOLA. Sorry!

Thanks! 1: Yes 2: M = MÅL - target is what I meant. You can read about reconnaissance in the manual (http://media.heatblur.se/AJS37_Manual_RC1.pdf) from page 363 onwards. You need to be on the ground and select master mode BER for the cartridges to be generated and selectable.

What are the details around these new data cartridges in the beta update? Yeah casual multiplayer flying is the exact issue I wanted to address with this (work-in-progress) feature. You can, while stationary on the ground, load a generated data cartridge. The first one is the closest enemy vehicle. If the target is moving a predicted point will be set as target point. A similar estimate is done when loading a SKU-target. You can now also change the margin of the mission-time (default is a little more than 5 minutes) by a keycommand (default LCtrl+LShift+M and LCtrl+LAlt+M). Mission cartridges for your M and SKU reconnaissance targets will also be generated when you set master-mode to BER. To select a cartridge open Kneeboard (RShift+K) and scroll to Ground crew settings (“]” key) and then select the cartridge with LCtrl+LShift+C and LCtrl+LAlt+C. You will also see target data for the cartridge like QFE. I want to add a little more features to this function, like accounting for terrain around the target.

There is fixes incoming for Rb-04 for AI by JediTeo in the next patch (which I think is Wednesday).

Yes it does look like the cross is misplaced. Thanks for the report!

The way I interpreted the RL manual is that the 3km cross is used to mark the target for bombing and then you follow the directions on the HUD as you would with a normal NAV-bombing. This is how it is implemented in DCS. No automatic measurements or something as implied above, it’s just up to the pilot to figure out if the cross is on the target and the computer more or less just handles the count-down to release. Real-life Viggen pilots mentioned that you could see individual buildings in the size-range of the Globen in Stockholm and ships contrasted to the sea but not much else hence I don’t think this mode was very useful. Please note that the next release of Viggen (likely OpenBeta on Wednesday) will include improvements to the accuracy of the bombing. Most important change I think is that I implemented a “catching-up” logic in the release interval where if the computer detects it is releasing long it will release more bombs at once so at least the final bombs will have correct ground interval (so 8 bombs before the target and 8 bombs after even if the first bombs start releasing long). It will not be able to compensate perfectly depending on how quickly the pilot changes attitude etc but tries to do its best to predict fast changes in altitude etc.

What do you mean can't load? Please describe the steps you did and what happened.

IIRC a Viggen-pilot once mentioned that they used CCIP-mode (I think he means the high-drag bombs) when flying “search and destroy”-missions (his term, not sure it is the official one). This mode isn’t super-dependent on correct QFE esp if using a longer release-interval. The DYK (dive) mode with low-drag bombs isn’t super dependent on correct QFE either.

ELINT Hi! The RWR in Viggen (and by extension the ELINT-functionality) works like this: when a unit in DCS has its radar signal picked up by the RWR or U22 antenna on the Viggen the type of unit is checked within a database located in the file “DCS World/mods/aircraft/AJS37/cockpit/scripts/RWR/init.lua”. If it doesn’t find an exact match for the type of unit it looks for a match for the broader category of units like SA-10SR->Air-defenses->Ground units. If it still doesn’t find a match it uses an algorithm that takes the max detection distance of the radar (within DCS!) and calculates an estimate of the PRF frequency, carrier frequency and scan-time. Most of the time the estimate comes close enough. The reason for using either broad categories or an algorithm is for “future-proofing” the module for whatever could be added to DCS at a later stage (like mods for example). What is probably happening here is that both of those radars have the exact same max detection value within DCS and the algorithm gives the same values based on that. If you give me the likely values of each of the radars I could add them to the database, or maybe the max detection range for one of the radars in DCS should be changed.

It should be fixed in the next release to open beta. Thanks for the reports!

This has been fixed now. Not in time for todays patch though, will (hopefully) be in the one after that. Thanks for the reports!

Yes, replay fidelity has improved significantly. From what I’ve seen there seems to be mostly divergence when on the ground now, like when using wheel brakes.

How to target individual ships with RB 04e? In the Mission Editor you can select which target in the row that the Rb04 should go after. You can select the first, second or third ship in the row. IRL this setting is on the actual missile, set by ground crew before take-off.

Look here: https://forums.eagle.ru/showthread.php?t=95985 I think minimum you'll need msbuild 2014 which is part of Visual Studio to write some connection to DCS. Apart from that you could use punch-cards if you'd like :) Realistically I think 100% of us devs are using Visual Studio as our main development environment and probably everyone has developed their own system. I am still hoping someone would create an interface for FlightGear though.

It was accidentally deleted. Will be back in next patch.

Ground info should be back in with whenever there is a new patch.

AJS-37 Viggen Crash to desktop The ground info page was accidentally deleted in one release but is back in (in our version). To get the ELINT-info to display you also need to be standing still on the ground + BER-mode. Haven’t checked if there is a problem with that as well but I think it should be pretty unrelated to the issue that was now fixed.

Here’s a summary of the issues we where able replicate and fix: - Random CTD happening at any point after when there is a radar transmitter in the mission and after you either set the mode-switch to BER or shut off the electricity (Caused by ELINT-code writing to file). - Random CTD when crashing hard into the ground. - Random exiting DCS when respawning. - CTD when activating radar display (either through A1 or A2 or through LANDNAV-mode) and then respawning (possibly needing to activate display again). Two of the issues where caused when trying to ensure code-robustness (ie memory clean-up Cobra mentioned) so it’s doubly unfortunate it hade the opposite effect.

If you can consistently replicate the issue, try removing all radars in the mission and see if you get the crash then. Btw, thanks for helping out guys. I am really sorry about this issue. Am trying to narrow down issues and I am right investigating two potential candidates: one when you crash and die instantly (ie you you crash hard into the ground) and one related to when ELINT-data is written to file (where the CTD might happen at the actual time of ELINT-export).

Do you guys have any emitting radars in your missions? Anything that makes the RWR beep?

Yes, it's not a priority though