[FIXED] AJS37 CTD

[Quip]

If you are in NAV, CK37 will calculate your position so that it knows where you are, even if you land. You can also change waypoins in NAV no problem, you can even load new cartridges while in NAV (flying). Not sure if that's possible or advisable in the real aircraft, but it's very possible in DCS.

 

 

I will repeat myself one last time:

 

NAV-BER-LS-NAV resets the CK37 and HUD to its "Take off" configuration. It's *the way* to do that, and the only way to get the HUD to display its take off mode once again upon landing.

[MYSE1234]

I will repeat myself one last time:

 

NAV-BER-LS-NAV resets the CK37 and HUD to its "Take off" configuration. It's *the way* to do that, and the only way to get the HUD to display its take off mode once again upon landing.

 

Yes, that part I agree with you, but it's not critical for the function of the jet and it's systems.

Edited June 2, 2020 by MYSE1234

[Quip]

Got you Quip, thanks for clearing this up into two different things!

Just a question regarding the take-off thing: what would happen if I manually enter a take-off heading for a starting base by using the (I think) BANA-GRÄNS. I am not at my sim computer, but I think then (at least) the HUD should show a (more or less) correct indication!?? Does it? :unsure:

 

 

That's a third thing in fact (I think, if I understand you correctly).

 

 

 

So here's a scenario.

 

 

1. You have a cartridge with the only runway in it (Swedish military bases at the time had only one runway and never two in parallel!), let's say it's a 09-27. So you load it and the pre-designated runway was the 09.

 

But now you need to takeoff and due to "things"...

 

 

2a ...you need to change to 27. In this case you just go to Bana/Gräns (runway/limit) and you press LS once more to switch to 27. In fact, you don't even need to do this as when you start rolling, the automatic reference point update which is made between 100 and 200 km/h will notice if the runway heading is reversed. Or more to the point: it will expect the runway to be the reverse one (27 in our case) if the actual heading (compass) differs from the supposed (BANA) by more than some 40 degrees. So as long as you're on the same runway, you're fine even if you don't manually change the runway heading

 

 

2b ...you need to takeoff from a taxiway with the heading 110. In this case you *need* to enter the correct heading in BANA (runway) manually. If you don't the automatic fix will completely mess up everything. Since your heading 110 is "close enough" to 90 it will tell the system "this is 90" and your navigation will be off by +20 degrees.

 

 

 

2c ......you need to takeoff from a taxiway with the heading 180. In this case you *need* to enter the correct heading in BANA (runway) manually. If you don't the automatic fix will completely mess up everything. Since your heading 180 is not close 090, the update will tell the system "this is 270" and your navigation will be off by -90 degrees.

 

 

So if you've landed at a random airport, not only do you need to do the NAV-BER-LS-NAV dance, but you must also make sure you have the correct heading setup. If you don't the auto reference update during take off will mess up your navigation.

 

Now an important point: If You *don't* do the "dance", then the system isn't in take off mode and won't do the update. This is why it doesn't matter to most sim-pilots. As far as teh CK37 is concerned, you have only flown at 0 km/h and at 0 meters for a while.

 

 

The HUD (as per your question) doesn't show any of this. This is something you can tell from the yellow marker on the CI/Compass.

 

During take off the HUD shows you three different displays: 1. the correct rotation speed (which switches to) 2. the correct climb attitude (with or without burners) (which switches to) 3. and the correct time to retract gear (which no one ever cares about in real life). This is what the NAV-BER-LS-NAV resets.

Edited June 2, 2020 by Quip

[Palten]

Hmm... I seem to be getting the same crash (memory out of control until CTD) by turning of the generator or putting throttle to stop.

 

I think I got the same today as me and Hilmerby tried to get around the BER-bug by turning the aircraft off before going to BERedskap, but the game froze.

[jojyrocks]

Just got it crashed after setting it BER done after landing at Visual setting.

 

 

My computer just froze up and had to restart coz not even ctr+alt+del could not get me out...after restarting, it directs me to the BIOS page. Miraculously after the second restart...went back to normal, phew..

 

 

I'll have to stay away from the Viggen for the time being until there is a solution that does not kill my PC.

 

 

 

 

 

My specs are as follows:

 

 

Intel I5-8500, MSI RTX 2070, 32GB RAM and 1TB SSD. Windows 10 pro 64.

[RagnarDa]

Can you give me the dcs.log? If you started DCS again it’s saved as DCS.old or something IIRC.

[jojyrocks]

Can you give me the dcs.log? If you started DCS again it’s saved as DCS.old or something IIRC.

dcs.log.old.doc

Edited June 9, 2020 by jojyrocks

[Mud]

I had a freeze / CTD when doing ESC > Setup Controls during a flight.

On the ramp this did not cause a crash.

 

Map: Caucasus

Specs in signature.

 

Best regards,

 

Mud

dcs.log

[RagnarDa]

I had a freeze / CTD when doing ESC > Setup Controls during a flight.

On the ramp this did not cause a crash.

 

Map: Caucasus

Specs in signature.

 

Best regards,

 

Mud

Thanks for the report but according to the log the crash is in the menu UI system or Lua hence not in Viggen. Could you maybe post this bug report in the DCS World section?

[RagnarDa]

[ATTACH]239189[/ATTACH]

Thanks too, but the log is from a flight of JF-17 and MiG-21 unfortunately and not a Viggen flight :(

[jojyrocks]

Would this help?

 

 

This is not the OLD. file. Just the log file.

 

 

But. I must say...when the crash happened. I had to hard reset my PC. I had to just switch off the main power coz even after several minutes, the PC would not respond.

 

Then after powering it on...sent me straight to the BIOS page. I was almost going to send it for repairs. But did the restart again, and somehow it worked, back to normal.

 

Don't wish to test it again.

 

 

 

I could not attach it before. coz the file simply would not upload back then. I could not send both.

dcs.log

[RagnarDa]

Thanks! Unfortunately neither that log file contains a Viggen flight. Totally understandable you dont want to try it again. Are you per chance running a overclock? From your desciption it sounds like maybe a over-temperature issue triggered by some infinite loop in Viggen code. What about RAM?

[jojyrocks]

I never overclock. My GPU is running on stock. MSI RTX Ventus OC. But I have not installed the software to control or OC the GPU. So far, I believe it runs on stock settings. It can be overclocked, but I don't bother about overclocking stuff.

 

 

This never happened before. But...like I said. After you land and then come to a stop just before taxiing. I turned it back to BER from Visual landing setting. That's when it crashed.

 

 

 

 

RAM is 32gb

 

 

 

CPU - I5 8500.