yoyo_332nd

Please explain me why you wanne do that. With three screens you configure DCS with three screens. Then, if your model has a 140 FoV limit, you will have a max FoV of 3x140=420 degrees. But you wont be able to place the monitors correctly. I can garentee you that 3x120=360 is more then enough. But then you would have to place your monitors in a triangle and stick your head between them from below or above... This is possible with beamers in a big room though. And with beamers you need some overlap for blending the views, so 3x140 might come in handy. I find 3x60=180 more then enough sitting in between the ends of my side monitors in a 60*/60*/60* placement for a full 180 degrees view. *=Degrees

A Helmet Mounted Cueing System is fixed to your Head Movement. In DCS, with TrackIR, it is a Center Monitor (or Beamer) Mounted Cueing System or CMMCS. It's fixed to your Center Monitor (or beamer). It is NOT tracking your head (Helmet). Rendering a HMCS with TrackIR in DCS Almost Completely Useless. If I turn my head (Helmet) 75 degrees to look at my right monitor, my Helmet Mounted Cueing System data stays at my Center Monitor. It left my Helmet... Becoming a Helmet Leaving Cueing System (HLCS)

But the HMCS doesn't follow your headmovement with TrackIR and by doing so is almost unusable.

I don't use fly-elise, but I know someone who has (for an other sim). I understand it is better to create some view overlap so fly-elise can better do it's merging. So instead of having 3x90 to get to 270, position the beamers at 90 degrees but let them display 100 or so degrees. With overlapping pixels.

Then you probably have configured DCS with one instead of three screens/viewports. With only one screen/viewport you can never get past 180 FoV. The CameraViewAngleLimits is per screen. If it is 120, you can get to 3x120=360.

The CameraViewAngleLimits variable is defined in the Views.lua files. They are mod specific and can be checked by the MP servers (if set by admin). And overwritten by every update...

Any aircraft with a vertical stabalizer will. The wind on the stab will push the tail to the right and, because the main gear is in front of the stab, the nose will rotate to the left into the wind. Use constant right rudder and maybe some left aileron to keep wings level. PS Storm Eunice was more then 10 m/s

https://forums.eagle.ru/topic/206282-subject-to-change-desired-f-16c-systems-and-payloads/#comment-206555

The %AppData% folder is a hidden folder. You can copy-paste your folder path in explorer and enter to it. Or type %AppData% in explorer to get in a AppData subfolder.

Hi Avantar, Thank you for this utility. I currently use it for my general commands. I love the Long Press option. I have found some small issues. It's been a long time since I read the whole topic, so it is possible some were already mentioned by others. Sorry, if that is the case. RS Mapper 0.0.52.0 · POVs NW doesn’t load properly into the POVs window from the .RSMapper file · POVs SP/LP/RL functionality doesn’t work as it does in Buttons section/window (doesn't give a filled checkbox when command exists) · POV NE SP/LP/RL functionality grays out · An F10 command assigned in a profile selects RS Mapper File Menu when executed · Long Press (LP) Continuous (Hold) becomes a Sticky Key instead of a Hold Key (default non-continuous is Pulse) · I would love to have a CTRL+S Save Shortcut · I would love if we could change all (sub)window sizes. Especially the “All mapped actions” window can’t be made higher. · I would love if the columns would Size All To Fit by default (Header and Contents) Thanks again for this great utility.

Why have you configured your setup as 1 monitor? Do you have your monitors in the same plane instead of tilted inwards to increase FoV..?