-MadCat-

The switch to the right, according to manual, is the "Heading data selector for INU alignment". Played around with it and didn't notice it having any invluence on the problem, too. Some more things I noticed: When manually programming waypoints in the PVI-800 withoug having any set up in the mission editor, the DTA/DH - submode correctly displays the heading when the DH/DTA switch on the autipilot panel is set to DH. Yet the display shows "000" for DTA when the switch on AP panel is on DTA. Now the scenario, when you set up 6 random waypoints in the mission editor. Not only does the PVI-800 work correctly with those set waypoints, it also correctly computes all the DTA and DH data if you reprogram those 6 waypoints. It's much like you "prime" the database with predefined data and make it accept new manually input data too. But beware, when you put the random waypoints in the mission editor right on top of each other and then cycle through them in cockpit, the HSI needles lock up. So placing 6 random waypoints in the editor could be seen as a treatment for the disease, but it's not a cure so far. Any further input is appreciated, thanks for all the feedback so far ! MadCat

Hello folks, once again I'm stuck with my ideas of how to solve or circumvent a problem. This time it's about reprogramming the PVI-800 on ramp. I like to just join custom self made mission and fly around, thus working out my route on site, in the cockpit. I'm familiar with how to program new waypoints, targets or airfields in the PVI-800 system. Now to the problem: How do I properly program the DTAs between waypoints into the PVI-800, so I can use the analogue HSI for on track navigation, without the need for the ABRIS? The supplied manual does not give too much help on that part of programming and everything I tried so far while programming the waypoints did fail. I didn't manage to program a DTA into the system, neither in programming nor in any other submode, it always is "000". That renders the DTA needle on the HSI useless when manually programming a route into the PVI-800 and you can only use DH. I am out of ideas, the manual is no great help, and nobody I asked online so far had an answer to that issue. I didn't find a thread in the forum discussing that, either. Note: When I plan the route in the mission editor, all waypoints and DTAs are properly set in the PVI-800 and ABRIS. I'm thankful for any help or comments! EDIT: Big thank you to all who contributed to the discussion and helped finding a solution! flankerOne knew how to make the PVI-800 compute the manually input waypoints, and posted the procedure here. Thanks to JG14_Smil too, who also really put some effort in finding a solution! Greetings MadCat

Perfectly works on : - AKG K-518 DJ - AKG K-242 HD (almost exclusively using it with these headphones) Fits on : - AKG K-701 (yet, due to the design, the clip sits rather high above the ear (lower LED at about eye level))

Hey Bigfoot! Yes, that's what I want to do, create a command that only puts the lever in the up position. The next step would be to create another command to put the lever in the down position, and repeat that for the right cut-off valve too. So at the end I'd have 2 commands for each lever that only moves it ONE way at a given button press. So far it worked perfectly fine for burst length, anti dust/ice, laser ranger, gun auto tracking/gunsight, landing gear up/down, rotor anti ice and the search light. It only is the cut-off levers that refuse to let me set a distinct up or down position.

Hey everyone, as the search function didn't yield sufficient answers to my problem, I try to ask this way. Inspired by this thread: http://forums.eagle.ru/showthread.php?p=1428587#post1428587 I started creating stateful button commands for BS2 to better suit the Warthog's throttle switches. So far everything worked out flawlessly and I created stateful commands for the Dust/Ice protection system, the burst lenght and the laser Standby/Off switches. However the Fuel Cut-Off levers are giving me a headache. This is the code I tried to implement into the keyboard.lua. {down = 3009, cockpit_device_id = 4, value_down = 0.0, name = "Cut-Off Valve Left Engine Close", category = "Ins Engines start-up control panel and levers"}, As with all the previous codes I implemented, the new command shows up in the designated options and I can assign a button to it. Now comes the annoying part. It works and lets me move the Cut-Off lever up, however on the next press, the lever goes down again, so the effect is exactly the same as if I'd assign a button to the normal "left engine cut-off valve" command, hence the purpose of a stateful command is not fulfilled. I rewrote the code now several times, tried several .lua files to implement it into, all with the same result that the newly assigned command still actuates the lever both ways. Altering the value_down = # also shows no effect, I even tried "0.5" to no avail. In addition to that, here are the parts from the clickabledata.lua and the devices.lua, where I got the values from. elements["EMERGENCY-BRAKE ENGINE-LEFT-PTR"] = { class = {class_type.TUMB, class_type.TUMB}, hint = LOCALIZE("Left engine cut-off valve"), device = devices.ENGINE_INTERFACE, action = {device_commands.Button_9,device_commands.Button_9}, arg = {554,554}, arg_value = {direction*1.0,-direction*1.0}, arg_lim = {{0.0, 1.0},{0.0, 1.0}}, updatable = true, use_OBB = true} devices["ENGINE_INTERFACE"] = 4 Maybe one of you guys knows what I'm doing wrong. I'd be thankful for everyone trying to help. Thanks so far, greetings MadCat

First post, here we go. Hi everyone, just want to quickly introduce myself. Maybe some people know/remember (hopefully good) me from the IL2 community in hyperlobby. As my trusty wingman retired from flight sims all together, and IL2 isn't the same to me as what it was some years ago, I'm looking for a fresh new start with the DCS series. So far I call BS1 and A-10 my rides, and it's only a matter of days for the 51 to arrive at my local airport/hard drive. P.S.: In the future, if time permits, I might look out for a serious squad with funny and easy going people outside the cockpit. On that note, native language is german yet english is no problem at all. That's about me, cya all in 41k ft :pilotfly: -=MadCat=-