Maulkin

Thanks I will check out those videos but I think your explanation has gotten me started pretty well.

Once I perform the takeoff it says the following: fly outbound TCN 067X on RAD/DME 065/5.5 at DME 5.5, fly heading 108 and intercept RAD/DME 089/13.5 I think I understand the first one to mean the configure the TACAN to 067X and follow it out to heading 065 for 5.5 miles..? What does it mean "at DME 5.5" and "intercept RAD/DME 089/13.5" ? How am I sure when I have passed turnpoint 1, so I know when to turn right to heading 108? Every YouTube video I find regarding navigation seems to rely on the JESTER menu and getting the guy in the back seat to set the HSI for you. But the tutorial mission does not seem to have a JESTER.

I am also having this problem and I have not been able to fix it. I am not exporting anything and I even deleted everything in this folder: C:\Users\<username>\Saved Games\DCS.openbeta Just to make sure there are no mods running I then loaded up the Release version of DCS and I am not having this problem at all. Just the beta. UPDATE: I just fixed it. To fix it I uninstalled the module (just the M-2000 module using the module manager) and then re-installed it.

Can't you add a deadzone yourself using the existing deadzone feature provided in the axis binding of the throttle?

Looks like the gates are open!

Well thanks for creating all of these training missions! They are brilliant!

Ok thanks! Are the training missions that Rudel chw provided based on the official missions or did he create them from scratch? I was a bit confused by his wording in his thread when he said "I'm in the process of editing some training missions for the JF-17, because I felt that the built-in training missions can be improved a bit, by adding voice-overs and making them longer to better explain things." It sounded like he was taking the existing missions and adding voiceovers. But he has a lot more missions there than I have in my training folder. I forgot about Chuck's guides! I will go find that for sure. I thought it was free for a month? Or are Deka doing it differently from the other modules?

Hey folks, I am trying out the JF-17 for the first time as part of the "free month" as I had heard this module was considered to be among the most complete. But when I went to start with the training I was surprised to only see two training missions: ColdStart, and Navigation. Am I missing something? Do I need to download the training missions separately? Thanks

It has been reported: https://forums.eagle.ru/showthread.php?p=4222396#post4222396

When you activate the landing light switch it starts the process to rotate the light from facing the ground to facing forward. While the model of the light does in fact rotate, the light emitted from it does not. The same thing happens with the backup landing light.

They completely rebuilt the cockpit geometry for the upcoming BS3 module so that means that all older texture maps will need to rebuilt from scratch. The said that the BS3 module will initially be released with only Russian textures but later on they will provide an English version. https://forums.eagle.ru/showpost.php?p=4206452&postcount=1

Out of curiosity, are all of these changes going to require a complete rework of all or most of the training missions that Baltic Dragon created? Sent from my SM-G935W8 using Tapatalk

"they were not mentioned in the changelog. Last update was in July this year." What went into that update? Sent from my P00A using Tapatalk

I was about to say:"No I never run mods of any kind." but then I remembered that I set up my multi-monitor display setup as a mod. When I disable my multi-monitor that appears to fix it! Thanks! Now I need to dig into my multi-monitor config to try and figure out what specifically is causing it....

All the YouTube vids show the targetting pod view to be in green monochrome and the AMPCD should be the only one to show the FLIR in greyscale but for me all three displays have the FLIR in greyscale. Do I have a problem here? Does anyone else have this? How do I resolve it?

Kneeboard builder does not appear to work anymore :( I just get the splash screen and then it is stuck there....

Actually that is what I started with, but this setup integrates the display with the interface in the same way a real MFD would in the real aircraft. In fact I still use the monitor for the center display of the Hornet or in the case of the Mirage I don't use the the MFDs at all. Right now I only use them with the A-10C, Harrier, and Hornet.

Parts used: 2 x Lilliput 8" 4:3 Um-80/c Mini USB Monitor(Non-Touch Screen) by Viviteq Inc https://www.amazon.ca/gp/product/B003LS95SG 1 x Thrustmaster MDF Cougar USB Cockpit Panels https://www.amazon.ca/Thrustmaster-2960708-Cougar-Cockpit-Panels/dp/B002HH9TRY I simply used double sided tape (Gorilla tape) to attach the panels to the monitors. The monitors have a USB connector on them so you can plug the panel into the monitor and it will use its power supply. The monitors also have their own deployable kickstand so no need to use the Cougar base. Keep in mind for this you will need 4 USB connections (both monitors need two each). I simply plugged the panels into the monitors, the monitors into a 4-port hub, and the hub into the back of my PC. So this way I am only using a single USB port. Then I exported the display of the left and right MFD's to the Lillput monitors: All said and done the cost (in CDN) was this: (2 x $160) + $100 + $50 (tax and customs) = $470

Is it possible to build this setup without the need of the HDMI control board (or even HDMI ports!) using this?: https://www.aliexpress.com/item/8-inch-TFT-LCD-USB-Powered-Monitor-Lilliput-UM-80-C-NOT-VGA-input-just-USB/32831656663.html This would not only reduce costs but I have a lot more USB ports than I do HDMI ports.

https://forums.eagle.ru/showthread.php?t=236087 In summary I was forced to uninstall the beta version, delete both the game folder and the folder in the "Saved Games" folder. Then reinstall everything from scratch.

To fix it I completely uninstalled the beta version, deleted the both the game folder as well as the saved game folder which contains configuration files. Reinstalled. Now everything appears to be working normally.

Actually I reported the same issue but with the TM Warthog throttle here: https://forums.eagle.ru/showthread.php?t=236087 It was not working for F-18 and F-5 but was working for F-14, A-10C, F-15C and M-2000C. To fix it I completely uninstalled the beta version, deleted the both the game folder as well as the saved game folder which contains configuration files. Reinstalled. Now everything appears to be working normally. This started up after installing the update last night. It was not having this problem a mere two days ago. huchanronaa, one thing you could try (before attempting an uninstall) is to go into the control configuration and clear all configurations for the plane, both keybindings and axis. Then manually re-bind all of the commands. I dont know if that might have worked or not but I was having other config issues so I felt a full reinstall was warranted.

I just tested the release version of DCS (version 2.5.4.27430) and I am not seeing this issue on any module there at all. So that eliminates the possibility that it is my hardware. That is what happens when you delete all of the lua files I mentioned. I also noted that some modules appear to be stuck in "game flight mode" where I have those arcade-like GUI elements on the screen even though that is turned off in my Options->Gameplay->Difficulties settings. But I am trying to only mention one issue at a time in this thread so I didn't bring it up. :)

Just updated to version 2.5.4.28615 tonight I have tried deleting the config lua files in the following directory: C:\Users\...\Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet\joystick The files are auto-generated once again. I re-set the axis to the correct ones but when I start the free flight instant action (or any mission for that matter) and attempt to use my throttles, I can see from the cockpit that the throttles do not move but the rudder pedals start to wiggle. The stick and pedals appear to actuate the correct controls but any axis bound to the throttle controls do not function. This is easily reproducible from any mission. I have also seen this problem with the F-5E module I use the TM Warthog stick and throttle, and Saitek rudder pedals. If I jump into the F-14 module everything works normally. I also tried the F-15, A-10C, M-2000C module and they also work normally.