PeterP

Here is the thread your looking for: DCS World and Multiple screen setups. but the files are attached here: http://forums.eagle.ru/showthread.php?p=1466722#post1466722 But again: EMC takes care of it and using this files is obsolete .

Cichlidfan is right: I enabled the option to receive only PM's from known contacts and friends. - I was getting tired to to explain how the search function of the forum works. There is a picture with a E-mail contact in my profile for 'urged support requests' (only visible for members) . @ Deadman You are in my friends list - try again. @doom Look up point 5 in the first post of this thread: A Plea for View-Export/Multi-head/TH Users. It contains every info you are looking for.

Delete the whole 'View' folder.

Don't worry about using up resources... Its footprint is barely measurable. PhantomMonitorFix only gets active once when DCS switches into simulation mode - and after it it 'sleeps'. It Will vastly lower your "preparation time" to start up DCS as you won't have to switch desktop profiles.

Yes (... #66 ... )

... and don't forget to swap the FFB axis for X and Y:

Please read : #201 / #211 Summary: Working with 8x8x8 will give you also good results, It really depends on the throw-ratio of your projectors and if you plan to put a full cockpit mock-up in it. The Throw ratio determines your head/cockpit clearance - keep in mind that there is only one ideal view-point for a distortion-less view in a cubic projection. My recommendation : Get a CAD program to visualise your plans in a 3d space (Google-sketchup is free and fully sufficient for this task) and get the data of the exact Throw-ratio and down-angel of the projectors you plan to use , and don't work with the absolute limits ! - always count in a 5% calculation error, so you won't have any 'surprises' or uncertainness while you build your cube. Ideally you would make you own measurements with a projector of your choice to get the absolute limits - you can't thrust the calculation-tools and manufacture data ! Here is a example how I did it for Flim :

Using the "PhantomMonitorFix" would be the best solution in your case. You would be able to keep the right monitor as Mainscreen while the DCS simulation is Rendered across both screens. Tip - place the exe or a shortcut of it in your startup folder , C:\Users\>User Name<\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup to lower your workload . So it is loaded when your system boots and you don't have to manually start it any more.

Axis response can be non-linear. (set by Software in DCS - setting a curve = non-linear response) Motor response can only be linear.(determined by Design of the motor/electronics and firmware of the FFBstick) So, when Motor absolute range and the axis relative position isn't matching you get a offset. (Not a problem with fixed-wing trimming as it only the relative position is needed , but a big problem on helicopters, because you need a absolute position. And this is only given when motors and axis are working linear.) To get what you want to do working you have to redesign the electronics inside your stick and use another firmware that let you change the linearity of the motor range. And you wouldn't be allowed to change it afterwards on a second software (DCS) . Here is a simple question that (I hope) helps you to understand where the problem is buried: (Let's assume you can change the linearity of your motors via the Logitech software) When you change the axis linearity in DCS - How should the firmware of your stick be aware of it? Further : Should ED be responsible to write a software that 'hacks' into the firmware of your stick and changes the motor-response?

This is not a bug - its a logical consequence. The Motors work linear and you can't mix it with a non-linear axis response. So: You can't use curves for force-trim system, like it is used in helicopters where absolute values are needed to hold the position.

Yes, your card performs faster in windowed mode because SoftTh doesn't works with enabled SLI. So you have to choose: Enabled SLI and windowed and also a slight wrong aspect-ratio (squeezed together) or single GPU and Fullscreen with right aspect.

Application key Use the attached Autohotkey script. (Run it as administrator) It maps Shift+F10 to send AppsKey+S while DCS is active. This is the used code:

and here is another undocumented source: Iris stopped the development because they had some "inside source" information that ED will next year only developed apps for android and the I-phone. ...please don't get me wrong. I'm not asking for any proof of any info / rumours. I just wanted to post also something without a value, just to compromise someone...

And use this following settings to get rid of the missing sea textures by using a 1:1 aspect ratio while maintaining right screen aspect via Softth. - Be aware that the F10 map will be buggy as you have missing (not visible) 180px at each side, but you can make everything visible at your main-monitor by using the ApplicationKey+S combo. options lua: SoftTH config : monitor lua :

Try this , my changes are marked in bold: options lua: SoftTH config : monitor lua :

Well, how about giving us some insight first? Your in-game settings, .. your SoftThconfig, ... and your desktop-layout would help very much to give you a answer .

>>> A Plea for View-Export/Multi-head/TH Users.

Have a look at this post: http://forums.eagle.ru/showthread.php?p=1641832#post1641832 Watch the video and compare it with the setup-lua "plan B". and the following post that shows the model. You can see that each view-port has a aspect-ratio of 1 in the lua file. If it is not 1:1 (Width /Height) you wouldn't be able to 'fold' them to a cube and the image would be distorted/not fitting at the edges. But because the Projectors are not able to show everything of the view-port we have to drop parts of it. In other words : DCS is rendering a full 1:1 image in 1280x1280 for each view-port but Flim is only able to project 1280x720 of it with the old projectors .

02-24-2011 >>> HDR Sun Glare Missalignment 05-22-2012 >>> A Plea for View-Export/Multi-head/TH Users. (issue #3) Edit: 03-06-2013 >>> Colours, Bloom & Sun all messed up in multi-monitor

replace your ...\DCS World\Bazar\Effects\PostMotionEffect\NightVisionGoogle\focus.png with the attached one , and your IR problems should be gone.

simply set V-sync on in-game ( make sure it is set to app.controlled in your gpu setting) and change line #331 in ...\Eagle Dynamics\DCS World\Config\graphics.cfg to : MaxFPS = 29; this will cap your fps to 30 and prevent any corruption. (...29 because DCS starts to count at the beginning of each frame, and not when it's finished , and the beginning starts with a 0 - and when you count 0 to 29 you get 30 ) Well, I don't use a Nvidea GPU and I can't tell you why your program fails... but i can tell you that it's the best to make changes yourself where they occur , instead asking a "man in the middle" to care about it.

Many thanks for the info. But I (we) really need a track , because the Shader/HDR settings and the problem is chained to your FOV/POV/screen-aspect and how much darkness (means : how much of the cockpit ) is visible when 'it' happened. Once I have seen it myself, I think that I'm able to determine which settings are needed that I can reproduce it and how to counteract it. And BTW - I don't have the time for fling around and hopping that I will see it.

Ok. Can someone post a Track where the problem occurs. - and tell me the exact screen settings you have used. (a screen-shot of the options>System screen should do the job) And ad additional system info and the used GPU+Drivers ... and I almost forgot: please give me a rough time frame (+/- 3min) when it happens in the track.

Hi Mustang, Please make a package of various 'Flavours' you would like to have tested . Send me a download link via PM and I will see what I can do at the next weekend/upcoming days. BTW: PM'd you my skype ID to short-cut long-winded written conversations.

From the readme: ...I really don't know what to add to make more clearer. ;) BTW: Which plane did you used for your first test? This Mod only works for the A-10C,ka-50 and P51-D out of the box. I posted a instruction how to make it 'compatible' for FC3 in posting #1.