skypickle

I mapped the function appropriately and I can hear the click noise but the dial doesnt move. I've seen this before in some modules where the the physical click with the mouse has to be registered.

Why did you edit the lua file? Did you get the master mode selector to work?

I asked him if he would release the dora missions separately but they will only be part of his campaign for the Anton.

Thank you. That topic was actually started by me but I was never notiified of a reply. I also just saw it in the routine of checking my old threads.

Looking forward to this. BTW, any good campaigns for the Dora?

figured it out. radios need apu power.

I decided to go back to iron flag. I could hear biff in the first three missions (Nellis) but in the next set (navigation) I could not heat him. Yes I checked the kneeboard and used the fragged freqs.

how does one show ground speed or IAS in cdu?

yes but i dont know how to use it. It talks about IFF and I just set mode 3A digits to squawk. What are all the selections for?

is there a campaign like that of iron flag is for the A10? Something that teaches the F5 strengths in a simple way?

What does that dial just to the the left of the throttle do? Cant find it in the manual or chuck's

I guess a recent update 'streamlined' these control options. Presently, I can only assign buttons to increase and decrease these controls. Previously I had mapped axes to lights (aux,console,engine,flight,flood,form) and radio volumes (AIM seeker, ILS, TCN,FM,UHF,VHF) How I can I restore these axis controls? In the clickabledata.lua file I did find this section for example --Light System Control Panel elements["PTR-LGHTCP-POSITION"] = default_3_position_small_tumb(_("Position Lights, FLASH/OFF/STEADY"), devices.LIGHT_SYSTEM, device_commands.Button_8, 287) elements["PTR-LGHTCP-FORMATION"] = default_axis(_("Formation Lights"), devices.LIGHT_SYSTEM, device_commands.Button_9, 288, nil, nil, nil, nil, nil, {70, -135},{90,-45}) elements["PTR-LGHTCP-ANTICOLLISION"] = electrically_held_switch(_("Anticollision Lights"), devices.LIGHT_SYSTEM, device_commands.Button_10, device_commands.Button_11, 289) elements["PTR-LGHTCP-ENG-INST"] = default_axis(_("Engine Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_1, 290, nil, nil, nil, nil, nil, {70, -135},{90,-45}) elements["PTR-LGHTCP-NOSE-ILLUM"] = default_2_position_small_tumb(_("Nose Illumination"), devices.LIGHT_SYSTEM, device_commands.Button_12, 291) elements["PTR-LGHTCP-FLIGHT-INST"] = default_axis(_("Flight Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_2, 292, nil, nil, nil, nil, nil, {70, -135},{180,-45}) elements["PTR-LGHTCP-AUX-INST"] = default_axis(_("Auxiliary Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_3, 293, nil, nil, nil, nil, nil, {70, -135},{140,-45}) elements["PTR-LGHTCP-SIGNAL-LTS"] = default_2_position_small_tumb(_("Signal Lights"), devices.LIGHT_SYSTEM, device_commands.Button_13, 294) elements["PTR-LGHTCP-ACCEL-COMP"] = default_2_position_small_tumb(_("Accelerometer & Compass Lights"), devices.LIGHT_SYSTEM,device_commands.Button_4, 295) elements["PTR-LGHTCP-FLOOD"] = default_axis(_("Flood Light"), devices.LIGHT_SYSTEM, device_commands.Button_5, 296, nil, nil, nil, nil, nil, {70, -135},{180,-55}) elements["PTR-LGHTCP-CONSOLE"] = default_axis(_("Console Light"), devices.LIGHT_SYSTEM, device_commands.Button_6, 297, nil, nil, nil, nil, nil, {70, -135},{180,-45}) elements["PTR-LIGHTS-LAND"] = default_3_position_tumb(_("Land Taxi Lights"), devices.LIGHT_SYSTEM, device_commands.Button_14, 655, false, false, {-0.1,0.1}, {{0,0.2},{0,0.2}}, 2) elements["PTR-ALCP-RSIL"] = default_axis(_("Refuel Status Indexer Lights"), devices.LIGHT_SYSTEM, device_commands.Button_15, 193, 0.0, nil, nil, nil, nil, {80, -45}) elements["PTR-ALCP-WPNSTA"] = default_axis(_("Weapon Station Lights. No function"), devices.LIGHT_SYSTEM, device_commands.Button_16, 195, 0.0, nil, nil, nil, nil, {90, -45}) -- No function in A-10C elements["PTR-ALCP-NVIS-LTS"] = default_3_position_tumb(_("Nightvision Lights"), devices.LIGHT_SYSTEM, device_commands.Button_17, 194, false, false, {-0.1,0.1}, {{0,0.2},{0,0.2}}, 2) elements["PTR-FSCP-RCVR-LT"] = default_axis(_("Refueling Lighting Dial") ,devices.LIGHT_SYSTEM, device_commands.Button_18, 116, 0.0, nil, nil, nil, nil, {90, -45}) elements["PTR-ALCP-HARSSAS"] = default_2_position_tumb(_("HARS-SAS Override/NORM"), devices.AUTOPILOT,device_commands.Button_31, 196) elements["PTR-ALCP-FDBAL-TEST"] = default_button(_("Fire Detect Bleed Air Test"), devices.SYS_CONTROLLER, device_commands.Button_4, 198,1, {0,1}) It clearly indicates that the lighting controls have axes but they are not showing up in the new LARGE controls setting screen.

In the clickabledata.lua file I did find this section for example --Light System Control Panel elements["PTR-LGHTCP-POSITION"] = default_3_position_small_tumb(_("Position Lights, FLASH/OFF/STEADY"), devices.LIGHT_SYSTEM, device_commands.Button_8, 287) elements["PTR-LGHTCP-FORMATION"] = default_axis(_("Formation Lights"), devices.LIGHT_SYSTEM, device_commands.Button_9, 288, nil, nil, nil, nil, nil, {70, -135},{90,-45}) elements["PTR-LGHTCP-ANTICOLLISION"] = electrically_held_switch(_("Anticollision Lights"), devices.LIGHT_SYSTEM, device_commands.Button_10, device_commands.Button_11, 289) elements["PTR-LGHTCP-ENG-INST"] = default_axis(_("Engine Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_1, 290, nil, nil, nil, nil, nil, {70, -135},{90,-45}) elements["PTR-LGHTCP-NOSE-ILLUM"] = default_2_position_small_tumb(_("Nose Illumination"), devices.LIGHT_SYSTEM, device_commands.Button_12, 291) elements["PTR-LGHTCP-FLIGHT-INST"] = default_axis(_("Flight Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_2, 292, nil, nil, nil, nil, nil, {70, -135},{180,-45}) elements["PTR-LGHTCP-AUX-INST"] = default_axis(_("Auxiliary Instruments Lights"), devices.LIGHT_SYSTEM, device_commands.Button_3, 293, nil, nil, nil, nil, nil, {70, -135},{140,-45}) elements["PTR-LGHTCP-SIGNAL-LTS"] = default_2_position_small_tumb(_("Signal Lights"), devices.LIGHT_SYSTEM, device_commands.Button_13, 294) elements["PTR-LGHTCP-ACCEL-COMP"] = default_2_position_small_tumb(_("Accelerometer & Compass Lights"), devices.LIGHT_SYSTEM,device_commands.Button_4, 295) elements["PTR-LGHTCP-FLOOD"] = default_axis(_("Flood Light"), devices.LIGHT_SYSTEM, device_commands.Button_5, 296, nil, nil, nil, nil, nil, {70, -135},{180,-55}) elements["PTR-LGHTCP-CONSOLE"] = default_axis(_("Console Light"), devices.LIGHT_SYSTEM, device_commands.Button_6, 297, nil, nil, nil, nil, nil, {70, -135},{180,-45}) elements["PTR-LIGHTS-LAND"] = default_3_position_tumb(_("Land Taxi Lights"), devices.LIGHT_SYSTEM, device_commands.Button_14, 655, false, false, {-0.1,0.1}, {{0,0.2},{0,0.2}}, 2) elements["PTR-ALCP-RSIL"] = default_axis(_("Refuel Status Indexer Lights"), devices.LIGHT_SYSTEM, device_commands.Button_15, 193, 0.0, nil, nil, nil, nil, {80, -45}) elements["PTR-ALCP-WPNSTA"] = default_axis(_("Weapon Station Lights. No function"), devices.LIGHT_SYSTEM, device_commands.Button_16, 195, 0.0, nil, nil, nil, nil, {90, -45}) -- No function in A-10C elements["PTR-ALCP-NVIS-LTS"] = default_3_position_tumb(_("Nightvision Lights"), devices.LIGHT_SYSTEM, device_commands.Button_17, 194, false, false, {-0.1,0.1}, {{0,0.2},{0,0.2}}, 2) elements["PTR-FSCP-RCVR-LT"] = default_axis(_("Refueling Lighting Dial") ,devices.LIGHT_SYSTEM, device_commands.Button_18, 116, 0.0, nil, nil, nil, nil, {90, -45}) elements["PTR-ALCP-HARSSAS"] = default_2_position_tumb(_("HARS-SAS Override/NORM"), devices.AUTOPILOT,device_commands.Button_31, 196) elements["PTR-ALCP-FDBAL-TEST"] = default_button(_("Fire Detect Bleed Air Test"), devices.SYS_CONTROLLER, device_commands.Button_4, 198,1, {0,1}) It clearly indicates that the lighting controls have axes but they are not showing up in the new LARGE controls setting screen. Help?

I guess a recent update 'streamlined' these control options. Presently, I can only assign buttons to increase and decrease these controls. Previously I had mapped axes to lights (aux,console,engine,flight,flood,form) and radio volumes (AIM seeker, ILS, TCN,FM,UHF,VHF) How I can I restore these axis controls?

Found it in the new UI layer.

I've been trying to find the button ID of the 'pinky switch' for the A10C-2. Its formal name is 'master exterior light switch' but I can find neither in the A10C_2 lua in the Export modules folder. I also looked in the clickabledata.lua in C:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C_2\Cockpit\Scripts Is there another place I can look to find a button ID?

Arctic came out with a 480? Where?

+1

There is a program called 'DCS moving map' that does exactly this with even better background maps https://movingmap.bergison.com/

Having a second monitor makes DCS so much more usable- either by allowing a web page about a topic you searched for, or perhaps your discord window, or reading a pdf , or whatever. BUT, if you are in VR, forget about it. IT becomes an exercise of peeking through cracks between the headset and your face. Imagine tho if you could push a button on your throttle and your second monitor gets mirrored to a part of your view. or even your whole view in your VR experience. Yes it breaks immersion, but so does peeking around the headset. And by allowing you to QUICKLY flash a window from your second desktop into the VR experience, it allows a sort of 'augmented reality' - you are in an aircraft but it's like you quickly peek at your smartphone.

Thank you for your detailed instruction. I am a little confused about the difference between the level acceleration takeoff and the limited power takeoff. In both cases you raise the helo to a hover and accelerate to about 50 knots and then pull the cyclic to get a max endurance climb at 500 ft/min. So how are they different? If your 'limited power' is less than the torque needed for an IGE hover on the perf page, you won't be able to take off. I would think that in these conditions, a rolling takeoff would be more effective as you could reach translational lift at the lower torque setting that limited power restricts you to.

Is this possible? How can i make the ‘screenshot’ assigned to a button?

https://wwsimstore.com/view/goods-details.html?id=316 Was part of a gift but not used. Mint. includes throttle and side panel with all the switches. $300 plus shipping

Purchased for offspring who did not like it. Includes desk mount, base, extension, and grip. Barely used. Mint. Seller located in MA. Selling for $250 plus shipping. Or I will meet you anywhere in a big city in MA to avoid shipping charges. EDIT: I did not realize their new orion2 is at this price point. I am dropping the price to $200 and it includes the desk mount as well as the extension.

Try running as admin