RagnarDa

Can you post a track? If not, do you have the dcs.log?

Are you able to replicate this in single player? If so, would you be able to post a track?

:thumbup:

The name of the airfield is displayed using the wrong charset (probably wide or unicode) and hence the ?? symbols. In the name there are probably a delete character that removes the new-line character, hence shifts everything after this one line up. I'm been meaning to fix this for a while but haven't gotten around to it (and nobody has asked about it yet either).

RB-15 can't select Bx8 to fix it What did you do to select Bx8?

Hej Oden! I am definitely interested in implementing those changes into the module itself!

I created a work-around for this issue now that should work. Sorry it took a while. Thanks for all the reports!

Japo32, here's a track showing recon M fix-taking (visual), transfer to SKU (double press) and a re-fix on the target to get speed and heading. Every time I overfly the ship I press TV. Let me know if it doesnt work for you. AJS37 Recon demo.trk

I've replicated and fixed the issue. Thanks for the excellent report!

Would you be able to post a track of when you are ejecting? I haven’t been able to do it.

Oh and one final idea: have any of you used any third party cartridge generating tool? Try opening the file c:/Program files/Eagle Dynamics/DCS World/mods/aircraft/AJS37/Cockpit/scripts/Navigationpanel/Device/init.lua and delete everything between line 303 to 377, so from the line under this: Data_cartridges = { to the line above this: } and by that removing all cartridges in the old data-cartridge system which is deprecated and should probably be removed altogether.

Guys, I am not able to reproduce the crash. I tried: 1. Running Cold start up in Nevada quick mission 2. Custom empty mission whit hot start from runway 3. Added enemy radar emitters (russian awacs and TOR) and set to BER-mode (so a ELINT-analysis is performed) 4. Deleted DCS_AJS37 folder in Saved games and tried a new empty mission 5. Added F10 markers All in single-player and changed cartridges at every step. Anything else I should try? Anyway, I'll do the pragmatic thing and disable the assertion so the game won't crash and instead show and error in dcs.log Most likely, judging from the warnings in unknowns log. It's also the issue with longitude being westward and probably then negative. We kind of try to give the opposite impression, but developing for DCS isn't any of ours day job. If I'd hoped to try to support myself on module-development I'd make quite a lot of other choices :D

What happens if you place a enemy unit in the mission? Thanks for helping me narrowing it down btw!

CTD when trying to change cartridge on Nevada Mezelf or unknown do you have any enemy ground units in the mission? Edit: what happens if you press ”ignore”?

TILS does not work anymore I have seen behavior with the TILS that isn’t right, just that I haven’t been able to reliably reproduce it. If I can’t do that and I go in and change stuff I might make it worse. Do we know if any airbase in particular is affected? A replay track would be ideal, and if you start in the air they are pretty reliable for at least a few minutes. It’s when you taxi on the ground they immediately deviate.

Oh and in case it's not clear, you can not combine two characters. And sorry for bringing in the escape character/hex thing, just ignore that and follow the instructions in the file.

Ha, I’ve made this years ago so I forgot how it worked exactly. So you are saying you put the L character in the string like this “LLLLL” and it played a 1750hz tone when painted by OSA in the game instead of 2800? How where you able to tell it was 1750hz?

Switching RWR audio The carrier frequency is used for categorizing the emitter on the recorder. They are categorized in two categories (A and B with some pivot frequency I don’t remember right now). This is then used in the post-mission analysis to determine the type of emitter, and you can see this on the ELINT-page in the DCS:Viggen kneeboarding. About lock-tone you are probably correct. Edit: I’d love if someone would take the time to flesh out the database. Especially for fighters it’s a bit lacking

I’m on my phone so I can’t listen, but apart from amplitude I believe you can do that. PRF 2500 would be “\031” (Lua escape character octal 31 = ascii 25 = times 100 = 2500). So something like this: { -- F-5 Type_Level4 = some number you’ll need to find in database.lua I believe, Type_Level3 = 1, --wsType_Fighter Type_Level2 = 1, --wsType_Airplane Type_Level1 = 1, --wsType_Air Search = "\031\031\031\031\031------------", -- Beep half second then silence two and a half second as example. I don’t know what would be correct for F-5 Lock = "\031\031\031\031\031-----", -- Here I just increased the frequency of the beeps Carrier_Frequency = 9000000, --Didn’t find the carrier frequency of the F-5 radar Scan_Area = 130, -- Radar come, in degrees },

No it’s a specific system I’ve made for the Viggen

Switching RWR audio Look at the letters. Each letter represents a tone that plays 0.1 seconds. The ‘-‘ symbol represents a 0.1 second pause. To know what tone it is look here: https://en.cppreference.com/w/cpp/language/ascii and look at the decimal column, then multiply that with 100 IIRC. So ‘L’ means 7600 hertz tone. Hope that helps.

Switching RWR audio Yes it’s only one sound that is pitched to make different tones. It looks first in the database you posted and if it doesn’t find a match it generates a likely PRF/pattern based on maximum radar-range of the emitter in DCS. You can add as many different entries in the database as you like, if you make any I could include it in the official release. Note that you can add broad categories in the database.

Thanks for the report! What airbase? Did you change the landing heading? Can you provide a track?

Yes we’ve seen it. No idea yet why it happens.

Reading your description I think I know exactly what is happening. The steering order gives a indication of what to do to hit the exact safety altitude over the target. As you get closer to the target you have less time to to correct so it will display a more drastic command even though the error is small (so if you are 1 millimeter off but also 1 millimeter away horizontally it would command a 45 degree climb/dive). I think this is correct behavior since there is no description of any function to reduce this and I have videos of the HUD when overflying waypoints where you clearly see the same effect (although on the other plane), but unfortunately no videos of the bombing mode. Hope that helps!