noderunner

Thanks. Post 144 got me close enough to where I got things mostly back on track now. I think there was something wrong with my CMSC_init.lua file which that post help me correct. I'm not sure what it was though.

I can't seem to figure it out. I managed to get the RWR and UHF exported and in the right positions, but no luck with CMSC or CMSP. I don't understand how the coordinates for CMSC or CMSP are completely different from other systems like RWR. The CMSC is just a little to the right and above the RWR, but when I plug in those coordinates relative to the RWR, I get nothing. I've tried randomly picking values for about 2+ hours and I get nothing. And yes, I am using the "new" style *_init.lua config that Icebraker figured out a few pages back. It just doesn't make any sense to me. It's like the way the game figures out the coordinates for the CMSC/CMSP are completely different than the UHF display, the digital clock, and the RWR. I wish there were some way that I could know for sure that my problem is the wrong coordinates. Maybe the problem is with my CMSP_init.lua? But how would I figure that out? If I comment out the render_purpose.GENERAL argument to the purposes function, should that remove the CMSP from displaying in the virtual cockpit all together? At least that way I would know my CMSP_init.lua seems to be set up right. On a side note, has anyone tried using the iControl DCS iPad app along with Helios? I'm using Gardoc's profile with Helios on a single 1920x1080 touchscreen, but I'd like to get the CDU exported to the iPad since there isn't a good place to export the actual CDU display in Gardoc's profile. I'm not sure how I could get these things working together though.

Nobody has any ideas? I still haven't been able to find a solution.

I'm having a hard time getting FC2 to display correctly on my Eyefinity setup and I'm looking for some advice. I'm running x3 displays, each display is a 27" LCD running at 1920x1200, for a total resolution of 5760x1200. My video cards are x2 ATI Radeon 5870's in crossfire mode. I can get the displays working fine in DCS: Blackshark and DCS: Warthog beta 4. The procedure is simple: Game video settings: Screens: 1 Resolution: 5760x1200 Aspect Ratio: 4.8 Then I simply edit the SnapViews.lua file and change this: Snap[9][13]["viewAngle"] = 89.777544238285 to this: Snap[9][13]["viewAngle"] = 219.777544238285. This procedure isn't working for me in FC2. I've read that I need to update the snapview for each aircraft in FC2, each aircraft being numbered as the first number after "Snap[#]", and the view being "13" for each one. I've tried that as well with no luck. I've also tried changing the view limits options in the Views.lua file from 20.00,120.00 to 20.00,220.00 and 240.00 with no luck. Each time I load up FC2, the view is very "zoomed in". If I keep pressing \ on the numpad to zoom out, I can get the display to look correct, but then my head movements don't work with TrackIR, as if the first person camera is stuck once I zoom out. Another oddity is that no matter how I tweak things in the Snapviews.lua or Views.lua file, the display doesn't change at all when I load up the game. From a width of 120 to 220 to 360 seems to have no effect on the display when I load up the game, nor does any tweaks to the viewAngle in the snapviews.lua file. I've looked for some documentation on the Snapviews.lua file to understand the settings a bit better, but what I've been able to google is pretty sparse. I've seen some youtube videos of other people running FC2 with eyefinity correctly so I'm pretty sure it's possible. Any help would be appreciated!

Thanks for the advice everyone. I'll just have to keep practicing. I've been thinking about a sport pilot license, so I've been doing a lot of sim practicing with the Accusim J-3 Piper Cub addon for FSX, and the ease of flying that aircraft has spoiled me!

I'm not a very skilled pilot, but flying the A-10 is the first time I've had this much trouble trimming the aircraft for a particular airspeed, and maintaining straight and level flight. I'm running Beta 4 and using the Thrustmaster Warthog HOTAS setup. I'm trying to make it through the "Take Off and Basic Maneuvers" training mission. I'm having a lot of trouble when I'm asked to maintain 180 knots at 7000 ft. In every other virtual aircraft I've flown, setting the trim for a particular angle of attack causes the aircraft to maintain a particular airspeed, even when you increase or decrease the engine RPM. Not so in the A-10. Why is this? Whenever I trim the AoA, no matter what my current airspeed is, making changes in the throttle doesn't simply result in a change of altitude, but the airspeed changes as well, and the aircraft starts bouncing up and down. I don't understand why this would be any different in the A-10? Does anyone know what engine RPM I should maintain in order to hold 180 knots straight and level? I'm finding this near impossible to accomplish. I'm also finding that the aircraft will bank just slightly left or right once I trim and let go of the stick. I keep having to make small corrections (1-3 degrees of bank). I don't know if that is supposed to happen or not. Since this isn't a prop-plane, I shouldn't have to worry about p-forces and other types of torque which would make the aircraft want to bank or turn. Is this supposed to happen? Or am I having some kind of input problem?

I didn't know that DCS had its own bezel management features. ATI will provide bezel management for Eyefinity in the 10.3 (March 2010) driver release that is set to come out some time next month. But the angles problem you are describing sounds to me like the "stretching" of the image that Eyefinity does to the side screens. That is something that Eyefinity does with every game, not just DCS. I don't know if there is a way to turn that off or not. Its purpose is to better simulate peripheral vision. I don't mind it so much but I understand some people don't like it.

Nevermind, I figured it out. If you set the graphical settings to using 3 screens and leave it at the strange 4.8 aspect ratio that it defaults to (instead of 16:9 like you do in most games) it seems to work.

Is anyone else successfully using an ATI Eyefinity setup with DCS Blackshark? I'm trying to use it across three screens, and it uses the correct resolution, but the aspect ratio is messed up and everything is stretched wider than it should be. Has anyone else had this problem?