I can't get L1/L2 to work

[pwnas]

Hello all virtual viggen pilots. I need your help in understanding what I am doing wrong when trying to get a landing waypoint (L1 or L2) to work.

 

I have made a very simple mission that starts me cold on the ground at Batumi. I have set up a single waypoint (B1) on my way to the landing waypoint Senaki-kolkhi. And that is the entire mission.

 

After starting the jet I load the data cartridge by turning the datapanel selector to REF/LOLA, IN/OUT switch to IN, enter "9099" and press LS. The first "9" starts to blink and after a few seconds the display shows all zeros indicating a successful read.

 

I flip the IN/OUT switch to OUT and turn the selector to AKT POS to verify that my flight plan has been loaded. If I press LS or B1 they show up as expected with direction and distance. But if I press L/MÅL nothing happens. (Actually, the destination indicator flickers for a fraction of a second but then returns to the previous selected waypoint).

 

If I go back into REF/LOLA + OUT and press L/MÅL it shows "901200" (Senaki-kolkhi) as expected.

 

If I ignore to verify the flight plan, take off and follow the navigation the computer does change to L1 after passing B1 (which is my last and only waypoint). But L1 does not point to the landing field and after a few seconds it automatically switches back to B1. If I turn the master mode selector to LANDING/NAV while L1 is active it immediately switches back to B1.

 

I thought that maybe I did something wrong when creating the mission. But I get the same behaviour if I try to enter a landing base manually from any mission. (Just to be clear. I configure a landing base by selecting REF/LOLA + IN, then entering "90XX" and press L/MÅL.)

 

Its almost like the airfield reference numbers are not working. Do I have to do anything special in order for them to work? They all show up nice in the kneeboard for me. Regardless, I could not get it to work even when manually entering coordinates in REF/LOLA and runway heading + TILS in Bana/GRÄNS.

 

I expect to be able to select the L1 waypoint at any time by pressing L/MÅL while in AKT/POS + OUT and then turn the master mode switch to LANDING/NAV to get directed to the landing field.

 

Have I misunderstood how this is supposed to work? Am I doing something wrong?

[randomTOTEN]

I just tried your scenario and everything worked properly. I don't know why you're having an error.. the only thing I can guess is that I used to have a lot of problems with CK37 but narrowed it down to short presses on the buttons seeming to cause problems. Keep the buttons pressed for about a second and hopefully that will help.

[TOViper]

...Have I misunderstood how this is supposed to work? Am I doing something wrong?

 

Reading for the first time nothing seems wrong to me.

In the past I found out guys having bad input configs.

Let me try this again: Do you have configured the button press for L/LMÅL with keyboard AND joystick (or mouse). Maybe you are pressing it, and for any reason another button is pressed at the same time?

 

 

Yesterday I flew some hours with the Viggen, and I didn't experience problems with taking off and landing (although it was Kutaisi).

[QuiGon]

First of all I want to commend you for your excellent description of the problem. I wish more people would describe their problems as detailed and precise as you did! :thumbup:

 

Now about the problem itself. I can't really see anything you did wrong there and wonder why it won't work for you. Personally I haven't done a flight in a while, where the pre-planned start and landing locations are not the same, so I can't say if that might cause issues. What I have done just yesterday was a flight where I changed my landing base midair, because I wanted to land on a different base then I started from. I did that by inputting the respective reference number and all worked fine. So I can confirm that this should work as intended and you said you tried it as well:

I thought that maybe I did something wrong when creating the mission. But I get the same behaviour if I try to enter a landing base manually from any mission. (Just to be clear. I configure a landing base by selecting REF/LOLA + IN, then entering "90XX" and press L/MÅL.)

The procedure seems to be absolutly correct and it really baffles me that it's not working for you. :dunno:

 

 

Just one thing that you haven't mentioned: Have you inserted the data cartridge before loading its data?

 

Edit: Also, try to use different air bases. Maybe it's the particular air base that has an issue.

Edited August 13, 2019 by QuiGon

[RagnarDa]

Is it possible you could record a track? Seems like it would be noticeable on a very short track

[pwnas]

Thank you all for the suggestions!

 

Keep the buttons pressed for about a second and hopefully that will help.

I don't think short presses on the datapanel is the issue. They all seem to register. I did try to do everything with long presses but it still does not work.

 

Do you have configured the button press for L/LMÅL with keyboard AND joystick (or mouse)

I have not bound any of the datapanel buttons (numbers or LS, MÅL) to any keys on purpose. I revied all my bindings and could not see anything obvious that would cause this. I also tried to unplug my stick, throttle and pedals and still got the same behaviour. So at least none of them have conflicting bindings.

 

Just one thing that you haven't mentioned: Have you inserted the data cartridge before loading its data?

 

Edit: Also, try to use different air bases. Maybe it's the particular air base that has an issue.

I do insert the data cartridge before loading it.

 

I also tried a few different air bases but all with the same result. I started an instant action mission and tried to enter a couple of different air bases by code "90XX" but I can't get L1 to show when pressing L/MÅL.

 

Is it possible you could record a track? Seems like it would be noticeable on a very short track

I recorded a track where I start up the jet (skipping any proper procedures to get it up and running fast) and then load the data cartridge and review the loaded data. You can see me stepping trough the flight plan and both LS and B1 looks good and can be selected, but L1 can not. I also look at what data is loaded for the three (LS, B1, L1) waypoints in REF/LOLA and Bana/GRÄNS and everything looks correct. Airport reference numbers, runway heading and TILS channel.

 

It sounds on you guys that what I have been doing should work. I think I might try to reinstall DCS and hope that will fix this since I seem to be the only one who has this problem.

no_L1.trk

[randomTOTEN]

you know you can just run a repair, you don't have to reinstall

"dcs_updater.exe repair"

[pwnas]

I found the issue!

 

I did not reinstall the game. I don't have dcs_updater.exe since I have the steam version, but I had steam verify the integrity of the game files and it found nothing. After that I removed all my settings from <my user>\Saved Games\DCS and then everything worked! I could select L1/L2 in my own missions and from instant action.

 

I restored my config piece by piece until I got to the point where it broke again. It was DCS\Config\options.lua. I had

"easyRadar" = true

and that apparently broke L1/L2 for me. So I restored all my config and changed easyRadar to false and that was it.

 

I don't even know what easyRadar is supposed to do, or what option it refers to in the GUI inside the game. But I am pretty sure that this behaviour is not by design :)

 

Thank you all for your suggestions.

[TOViper]

I found the issue!

 

I did not reinstall the game. I don't have dcs_updater.exe since I have the steam version, but I had steam verify the integrity of the game files and it found nothing. After that I removed all my settings from <my user>\Saved Games\DCS and then everything worked! I could select L1/L2 in my own missions and from instant action.

 

I restored my config piece by piece until I got to the point where it broke again. It was DCS\Config\options.lua. I had

"easyRadar" = true

and that apparently broke L1/L2 for me. So I restored all my config and changed easyRadar to false and that was it.

 

I don't even know what easyRadar is supposed to do, or what option it refers to in the GUI inside the game. But I am pretty sure that this behaviour is not by design :)

 

Thank you all for your suggestions.

 

 

Wow, nice find! :thumbup: