Nerull

Found it! Thanks to a post on reddit ( )! I checked my Throttle lua file and it had ["name"] = "HOTAS Slew Horizontal", ["removed"] = {[1]} ["name"] = "HOTAS Slew Vertical",["removed"] = {[1] in it, which blocked the axis availablity. I removed the lines And now the axis is available: Thanks for the help!!

I tried to assign the axis to slew, but the option isn't available, it's not in the clearer blue like the available options Clicking add gets no reponse when I have the slew axis command selected either. Funny thing is that DCS does recognize the joy axis input. When I tried on a "light blue" area (rudder in this case) it actually detected and selected the joy_X or joy_Y inputs.

I got mine a while ago (#331), installed it and tested it in the windows config and it worked immediately and perfectly. Only just started having some time to play DCS in my beloved A10C, but the slew isn't recognized :'( I tried configuring it as an axis, but the option isn't available in the control config panel. I'm probably missing something that'll make me facepalm once I'm told, but I'm willing to take that chance. How do I configure my slew to work??

:doh::doh::doh::doh::doh: It seems the little "always on top" for screen 2 was not ticked anymore, hence the disappearing. Thanks again for the help Capt Zeen! I'll crawl under a rock in shame for a while now...

Thanks for the feedback Capt Zeen. I checked that the "full screen" and "disable aero interface" were not clicked But the problem remains. The screens have been resized, but my bottom screen is only a 19" one (27" for the main). So that should be ok. Funny thing is, that although you can't see it on my screenshots the "Helios Control Center" panel is visible, but not the rest of the helios panel, which is indeed hidden by dcs. I placed it on the lower screen but it doesn't show up on the screenshot. So basically part of Helios is on top but the main part is hidden. I'm using your export.lua as well. Thx for the help, I'm hoping you might still have a brilliant insight to help me enable Helios. Bye!

Hi all! I'm in a bit of a pickle and reading the previous helios threads didn't help. so: I have a dual screen setup (one on top of the other) and want to use helios on my 2nd monitor. I followed the steps described in https://forums.eagle.ru/showthread.php?t=125195 but to no avail. When I start Helios it shows on my 2nd screen: But when I start DCS: 1.only the MFCDs are exported 2.it looks as if Helios is hidden "behind" the black background of DCS I've used this export.lua for a while (used to work before 1.5) and the MFCDs export, so I suppose it's not too bad: Any clues as to what I'm doing wrong? MDP-DS-ALL export.lua

I have the same GTX970 and used to be able to run at 60-70FPS too. Unfortunately I've had some issues ( http://forums.eagle.ru/showthread.php?p=2394701#post2394701 ) and I'm now using UltrMFCD to export my screens, but I'm stuck at 30FPS (max, goes down to 21) since I'm running in windowed mode. I'm no expert in all the settings, any advice on what to change to get some decent FPS without putting everything in low res? (having spent the money ont the GTX it makes me miserable to run in low resolution)

My config worked up untill a week ago, then: Something changed somewhere and now: I have 2 screens (1920x1080 on top, 1280x1024 on the bottom) and use my top screen as main and the bottom screen for my MFCDs. It all used to work perfectly, but since I re-installed after trying VirtualCockpit (with my android tablet) the bottom screen is recognized (I get the Softth logo and my mouse pointer can get there), but the MFCDs stop at the bottom of the top screen! My profile's pretty simple: The Softth config looks OK: But the MFCDs are not showing up on the bottom screen. Anybody have any clue as to what may cause this? I re-installed the whole game twice already, but to no avail.

I used to have it figured out but... Something changed somewhere and now: I have 2 screens (1920x1080 on top, 1280x1024 on the bottom) and use my top screen as main and the bottom screen for my MFCDs. It all used to work perfectly, but since I re-installed after trying VirtualCockpit (with my android tablet) the bottom screen is recognized (I get the Softth logo and my mouse pointer can get there), but the MFCDs stop at the bottom of the top screen! My profile's pretty simple: The Softth config looks OK: But the MFCDs are not showing up on the bottom screen. Anybody have any clue as to what may cause this? I re-installed the whole game twice already, but to no avail.

Best advice I can give you is checking out this link: http://www.digitalcombatsimulator.com/en/files/214771/ It'll clarify a lot and if you follow the guide you should get there with a bit of searching. It worked for me ...... up until my actual problem (see post below :'( )

ALT, like in Altitude: AP keeps you plane at the same altitude, not caring about your roll or yaw input. PATH keeps your nose pointing towards where it was pointing when you engaged the AP. It keeps the plane in the same path as you started (can stall you if your power's too low :) ) 3rd position (middle one, don't remember the exact abbreviation) keeps you going straight and level.

Why pause TrackIR? When I press "RCTRL + numpad0" I go into padlock view and TrackIR doesn't do anything anymore, no need to pause it. Am I the only one with this lucky fluke?

When you follow JTAC procedures (receiving info then readback) the JTAC sends info, also resulting in the "NOTE" popup

I don't feel like making hte calculation ,but your reasoning is based on Bernouilli's principle () and the ideal gas law (pV=nRt). But there's something missing in your calculation. It's not taking into account that with colder air you have more air density at the turbine inlet and in the combustion chamber. Higher air density means more oxygen, which means a better combustion of fuel, which means more energy is released. And since more air mass is injected in the engine and heated to the engine exhaust temperature you get more volumetric air at the exhaust than with hot air at the inlet, resulting in more thrust.

Personally I always put on autolase for 12s in the GBU setup. One important thing not to forget when designating the SPI is that the laser must be painting the target when you set SPI, otherwise you'll actually be putting a point on the floor behind your target as SPI (it's explained fully on the forum somewhere)