Hba8103

Why you gotta remind us that 2009 was a almost a decade ago....got people feeling old...:(

Is there anyway to adjust the vertical rotation around the x-axis (V-ANGLE)? In previous versions, the game would access server.lua or SnapViewsDefault.lua, which allowed you to change the vertical rotation and save it. I've changed in multiple places and the angle still remains at the defaault -26 degrees. I am using 3 screen setup with Track IR. My two outside screens dip down at weird angles. I noticed that if I lifted my head then the horizon across all 3 screens became flat. This is why I altered the setting originally. It was perfect. Now it seems that changing the value does nothing. Can anybody assist?

I'm from iRacimg too and the multi-monitor support for DCS is not as thought out as iRacing. It took me a while to get things setup "properly". I kept wanting to be able to see the HSI on my screen, like most of the videos on YouTube. When I did this, I could see the wings tilting forward on my side screens. When I turned my head with TrackIR, the horizon would be at an angle. I couldn't see all of the HUD symbology. No matter what I tried, the image seemed to be wrong or stretched out. It's your FOV. You need to choose the option to render to screens separately. You need to modify the 3screen.lua file to align the screens. If your screens are properly aligned in iRacing and you have a proper FOV there, you can simply take that FOV and divide by 3. This is the proper FOV for DCS as it uses the angle to project to each monitor. For my setup in iRacing my FOV is around 165 degrees meaning my FOV in DCS is around 55 degrees. Now, this will seem to push your face up against the front of the cockpit, but this is not the case. It is what the pilot would see, and at the same size as the pilot would see if he/she were looking through a 16:9 monitor....unless of course you're using a 4:3 ratio monitor. The point is, the monitor covers very little vertical area, so you won't be able to see your HSI. If you're using track IR, however, and tilt your head down slightly then you will. Think of it like this. Can the pilot see his HSI, all of his MFCD's etc. while looking out the front glass through the HUD? Sure he can. Can he read the HSI while looking out through the HUD? No...not at all. Just like you can't look out the window of your car front window and read your speedometer at the same time. You have to tilt your head a little and change your focus. When you get the FOV correct, as you turn your head, everything remains flat and in the correct proportions. Period. Your monitor doesn't give you the ability to fully peer into the virtual world. Only a window. This is the same principle used at iRacing to properly set up your FOV. Hope this helps.

Agree. For me. I built my rig for iRacing, which has an excellent system for multi screen use and proper FOV. My screens are 21" from my face. They sit directly behind my steering wheel. The panels right above my knee IRL would be the engine gauges on the A-10. My screen IRL stops about 8" above this. Therefore, my view (what many assume is their face being pressed against the cockpit) could not include the gauges. This provides a realistic FOV. I also use TraxkIR and 3 screens. Needless to say that if my FOV is not set properly I get distortion on the side screens. With the correct FOV I see what my monitor size and position allows me to see. When I rotate my head the view stays level and straight. No warping. When I look down, I see the ADI, HSI, etc. just as IRL if you looked down to focus on your instruments or speedometer while driving.

I'm a noob so take with a grain of salt, but I think there are several issues. 1. Your view on screen will be impossible to reconcile fully with what they see, especially if your screen is 16x9. How could you expect to see both the HUD and gauges in the same FOV if your window to that view is so narrow (vertical). I think the proper view appears to be closer to the screen. Think of it like this. The pilot might be able to "see" the gauges below, but he can't read them. He has to change focus and look down to actually read them. TrackIR simulates this by having you tilt your head down a little to be able to read them. Don't worry if they're not in your immediate field of view. Another way to think of it. When driving you can technically see your gauges, speedometer. But you would be lying if you told me you could read the gauges without shifting focus down. Think of the screen (because it is narrow) as your area of focus....or you can buy a bigger screen. 2. In the images, your head appears to be higher and the angle tilted down by a significant amount. Try directly adjusting the LUA files to force the settings to what you prefer.

I see a blank space above (am using an iPad). No video or link for video. Am I missing something or did your video not post?

Interesting footage that I hadn't until now.

I think it is done because it is the correct FOV and I'm not sure you can change or scale things on the HUD without messing up the correlation. This game does a poor job of enabling 3 screen setups and proper FOV. Our monitors are 16:9 for the most part. You might not be able to see your MFCD's for example, as the screen height is too shallow to provide that view. Yiu should be able to tell by looking at the scale of the cockpit around you. For example, if you have a 24" monitor, does the entire width of the cockpit fit on the center screen? More than likely it shouldn't (depending on how far away you sit). If you look at the pic above from the video, you can tell the the MFCD's and the portions outlined in black/yellow decals stick out further than your shoulders. The components in game should be the same size as they are IRL. It seems too close, but is probably the right distance. You're probably trying to see your MFCD's and ADI in the screen at the same time as you look through the HUD. You can see them IRL, but you can't focus on them (i.e. you can't see them) without tilting your head down. Same way when driving and focusing down the road you can't read your speed from the speedometer (unless you have HUD in car). You have to tilt your head down to see accurate speed. If your monitors are larger and you have Vertical coverage, then you will see the MFCD and ADI,but even then you won't read them without shifting focus. I have 3 screens at 60 degrees apart. I send separate signal to each monitor. I used iRacing FOV calculator to determine FOV and then divided by 3. Ended up with 60 for FOV. This gave the proper view in game for A-10c. Fairly certain the setup is dimensionally correct. If I adjust to something too big or small, there are skewed objects on my side monitors. If my FOV is not correct, there is a bend in the horizon near the bezels of my monitors. When set correct, the horizon stays flat as I move my head left to right. If I shift my POV back slightly, I can see the wings of the plane almost ahead of me at ta strange angle. I'm fairly certain this is the correct view, meaning that the HUD should be in the proper place on your screen without modifying the HUD file. My 2 cents for what it's worth.

I thought China FWD short would change the Mav FOV and China FWD long would slew to TGP or current SPI. If you are switched to MarkPoint does the MarkPoint become the SPI? I thought China AFT long slew all sensors to MarkPoint? I'm super noob, so just trying to understand the workflow. Are you saying China AFT long to slew to MkPoint. Then as you change MkPoint and the next Mav is slewing, use the China FWD short to change FOV to help it lock?

The only reason I have vjoy is for DCS. My rig was primarily for driving games, thus I have racing pedals and no real place for rudder pedals. In order to get my pedals to work as a rudder, I had to use vjoy. It works fine in 1.5.3., so it was something that changed in DCS that caused the conflict.

I too keep failing this mission (practice). I can complete, but I would like to be confident I can complete the maneuvers correctly. The main issue I have is when I think I've nailed it....it tells me something was incorrect. At other times when I know I messed up, it tells me that I executed correctly. When I try to wait to build speed for the Immelman, it tells me 'You failed to do that correctly' and I haven't initiated any move. Next time I attempt around 265 kias, which is not really enough and airspeed and I don't perform correctly at all, and it tells me excellent job. I noticed in Recon's video where he started at too slow a speed and was barely able to control plane on top of Immelman, but passed. I understand things have been updated since his videos. Why not have the aerobatic component start at higher altitude with a split s....then you have the speed to complete the Immelman in quick succession. [Are there specific locations in space that a maneuver has to start or occur to pass? Are there other parameters that are required that I might have missed in the documentation?] Edit: Missed your comment below the Recon video with the link to required parameters.

Yes, they said it was related to FFB devices. I unplugged (power) and disconnected the USB from my Fanatec CSWv2. Did not work for me. Only thing that worked was reverting to 1.5.3. There have been some updates to 1.5.4 in the last few days, but I probably won't update until they find a reliable solution. Glad you mentioned this......was going to log onto iRacing..and my wheel is still disconnected....LOL

Trim stopped working for me when I upgraded to 1.5.4. Reverted to 1.5.3. and everything was back to normal. By the way, I use vjoy to correct the input for my rudder pedals. My rig was built for iRacing, so set up with a 3 pedal set. The controller box only sends signal as 0 not depressed and 4095 fully depressed. So had to use vjoy to emulate controller and another program to invert and combine my throttle and clutch into a single axis. Tried other setups to combine axis in DCS, but nothing worked. Anyway, you didn't mention what version of the software you had the issue with. Was it 1.5.4.xxxx or 1.5.3?

Your FOV isn't set properly...unless the buildings were you live are all tilted backwards? You've settled for an inaccurate view.

Did you have to do anything special to get the module to work in the steam version of DCS World?