PeterP

I restructured the mod and edited the readme to prevent such incompatibility when a module isn't installed. Please reload : http://forums.eagle.ru/showthread.php?p=1541311#post1541311 These files only take care of the view-ports and work absolute independent from a active Helios installation . You have to consult the Helios documentation and the appropriate threads for help how to get the gauges/buttons/whatever to work with DCS World 1.2.5. - isn't it obvious?

Just install DCS World on your SSD. Once this is done, DCS World will leave a entry in your registry. FC3 will than recognize itself where it has to be installed without the need to tell it the path.

Did you delete the newly added Ka-50 folder?

Does this mean you don't have the Ka-50 installed ? If yes, give this a try: go to ..\DCS World\Mods\aircrafts\.. an delete the newly added Ka-50 folder. And also use the default "1 SCREEN" setting in a windowed configuration with the new A-10C files - just to find out if it's a broken lua or the files that are causing it. Edit: Made a test with de-installed Ka-50 and had the same symptoms. Removing the ..\DCS World\Mods\aircrafts\Ka-50 folder fixed it.

Yes, your "MultiMonitor.lua" is broken. Fix this as Kuky wrote. Also read here to get a better understanding how the 'monitorsetup.lua' works. >>> http://forums.eagle.ru/showthread.php?p=1469638#post1469638 No need to set your left screen as main when you use the 'Phantommonitorfix'. Tip - place the exe or a shortcut of this skript it in your startup folder , C:Users>User Name<AppDataRoamingMicrosoftWindowsStart MenuProgramsStartup to lower your workload . So it is loaded when your system boots and you don't have to manually start it any more. - It uses no measurable recurrences and only gets active when DCS.exe is loaded. But it would be better when you would create a Eyefinity group - so all 3screens are detected as a single one , so you can run full-screen. (you can also save this mode as pre-set in CCC - so you can switch easily and don't have to set up every time you run DCS.) Keep also in mind that the 3Camera setting is not really made for a planar TH setup. It is made for at least angled displays or , much better, a . - it also eats up a lot of resources , as the scene get rendered three times. This post explains a lot : http://forums.eagle.ru/showthread.php?p=1426370#post1426370 If you suffer of low frame-rates I would suggest you run the 1Camera setting. - but not in landscape, as the possibility is high that you will also run into other problems with your FOV: Try instead portrait, because combat flight sims are not '2 dimensional' - so having a narrow band in the horizontal will not help you much with your situation awareness. - sure , you can fly a big air-liner like this - but not a combat plane.

Did now the same what you described with the latest DCS 1.2.5 (non STEAM) - I did set DCS to 1600x900 windowed and used the "Export Example" monitorsetup.lua with both variants (In-cockpit off and on) - both works - as expected. Please tell us some more what exactly you did and which exact version you are using. (is your 'monitorsetup.lua' intact and does it use the new view-port names?) Re-load my files to be 100% sure you are using the right ones - and do it again.

...in the meantime, - watch this:

If the linked post and the included readme doesn't provide enough info for you - than: Yes ! Read the whole thread and follow each single link...

Try this >>> http://forums.eagle.ru/showthread.php?p=1541311#post1541311

post #34 sums it all up.

No - I won't open it. But here is a image that show how it works: The collective moves an axis that is directly attached to a potentiometer.

Tip: Update post #1 when it's solved.

Here is a tip ;):) : Make sure your model will withstand such investigations >>> Bell UH-1H rotor mast orientation

This mod is outdated and not compatible with the new 6DOF cockpits. - it has also not the new "Shouldersize" feature that came with 1.2.5. - I suggest using this one: http://forums.eagle.ru/showthread.php?t=96116

I think it's time for new numbers again - this time in relation to the cabin floor: Facts: Now the Mast is tilted 1.3° forward - according to the document that Nate posted it has to be 5°. This opens another question: Lets assume the mast gets "fixed" and will be tilted 3.7° degrees more forward - so it will be 85° from the floor-level . This will mean that the mast will be tilted 2.3° forward in relation to the ground/skids . (2.7°+85°)-90° = 2.3° Is the angel of the skids right? EDIT: I found a image that seems to show the same skid model as it is used in-game. (keep in mind that this Huey seems to be fully loaded . The picture also gives no hint if the rotors are running and on load- so this measurement can be only a estimate.) And also notice that the mast is tilted forward in relation to the cabin-floor. Image source >>> http://commons.wikimedia.org/wiki/File:UH-1H_taking_off_at_Hohenfels_Training_Area_2010.jpg

Played last nigh around with the XM60 reticle again, while waiting for a new Huey update... This is the old reverence that I used for the reticle >>> Update on Development Progress But after some research I changed it to this: And this is the reverence that I used: Whoever thinks he/she needs it changed too : Download it below. z_UH-1H_XM60E1_5 _80-MILreticle edit.rar

Just trying to fill this thread with some numbers: (...having some numbers makes every discussion much easier) No - you didn't answered my question(s).

Should be no problem. If all four outputs can work independent at the same time ,you are able to create a "Eyefinity+1" group - and this works just like Two screens in extended mode . - Windows sees your Eyefinty group as a single monitor. - so you will have Two monitors reported in the desktop properties.

No - some sort of CPU throttling is at work. This is the only answer how your multiplier can change dynamically. And at least a sentence about this App must be found in your motherboard/manufacture documentation.

...or simply use this and examine the changes:

Please answer this: What have the skid dimension/design to do with the mast orientation? and how can this relation be important ? (regarding to your more than questionable comparison shots with the angle drawing - this "comparison" clearly using two different skids and your white line in the DCS shot isn't accurate.) Just to give you another idea: Imagine the Mi8 is fully loaded and the main gears are almost flat... - where is the 'neutral' position now? Further: How exactly do you define "Neutral" on a cyclic ?

Did you notice that the multiplier jumps between 32 an 8 ? - this changes the core-speed from 3192 MHz to 798 MHz. This is causing the stutters. I don't know why it does this on your system while DCS is running , but here is one possible fix : Disable Enhanced Intel SpeedStep Technology (EIST) Open the BIOS settings during a reboot and look through the advanced or chipset settings and turn off EIST there. Another option is to examine you power-profile and change it to 'high performance' or similar and/or create a power-profile that disables EIST when the DCS.exe is running. - please look also into your motherboard documentation for more info.

EMC is broken with the current DCS version. DCS World changed the registry entries for each module frequently in the past. EMC hasn't been updated to identify these changes - so it can't see which module is installed.

I answered how to make these missing commands assignable here >>> http://forums.eagle.ru/showthread.php?p=1850626#post1850626

This happens every time when a new command was introduced by the developer while you are using a controller profile that was created before the developer added these new commands. The fix is very simple, but has a drastic consequence: You have to Delete the current used profile and rebuild it from the new default joystick file. This will sadly also force you to re-assign your profile from scratch. 1. First create a HTML -> [MAKE HTML] - so you have it easier to reassign it again by looking up how your old profile was set-up. 2. Highlight the controller with the missing commands and click -> [LOAD PROFILE]. and navigate to the input folder of the module/plane you want to update and chose the default.lua in the joystick folder. Example path for the FC3-Su25: ..Eagle DynamicsDCS WorldModsaircraftsFlaming CliffsInputsu-25joystickdefault.lua It's basically the same procedure like shown in this vid: Now you should be able to assign every command with the chosen controller. - open the related HTML you created before the 'reset' , to see how it was set-up and re-assign it again. You will have to redo it for every controller that has this missing 'Greyed-out' bindings to make them assignable (...as long the developer allowed it). There is also a method to do it by coping the missing new lines/instructions into your old profile with a file-editor. This will keep your old bindings intact - but this is only advisable if you are able to read the Lua code and you are really sure what you are doing. - Beware: the slightest typo in the syntax can brake your profile - so I wont describe this procedure here, because 'fixing' a old profile can take longer and is more complicated as doing it via the in-game GUI. If you want to learn more about it : Head over here for a example how to 'teach' a outdated profile the commands for the Kneeboard >>> kneeboard not mappable to my joystick