goon3r

Tried these but made little difference. Do you mind loading up that UN Pilot Mission 6 and see what FPS you get at mission start with the equivalent settings ?

Yeah, its off now. Still no difference.

Thanks for the reply. I tried v-sync but no difference. I've found that reducing water and visib to medium I can get an extra ~10fps in that same misson start. Tried a few other settings but nothing else seems to make much of a difference. Will try making some more adjustments and report back.

Recently upgraded to a 1080TI and was planning to get a 4k Monitor in the near future, however I'm noticing that my FPS is very low in some situations with my current 2560 x 1440 resolution. Maybe my expectations are too high for my machine (4790K with 16GB RAM) ? Most of my gaming is on the 1.5 Stable version. I loaded up the Huey UN campaign mission #6 today and had FPS in the 17-20 range. Once I get up in the air, I rarely drop below 60 fps, but once I get back around the FARP the fps deteriorates badly. Makes landing much less fun. Any recommendations ? My current settings are below:

well, I noticed that I was keeping my throttle at 0% when the mission starts so in my case I had to increase. I guess this is just a general DCS behavior on mission load and the huey being unstable as it is, reacts worse than the ka-50 by comparision.

New huey pilot here, with a weird issue. When I begin any of the missions that start you in the air, the huey immediately starts spinning uncontrollably before I can make any control inputs. 30% of the time I am able to make corrections and avoid breaking the rotors. In general, when I am able to get control the huey it is still unpleasant to fly and seems like I am fighting some other inputs, but that may be down to my inexperience. This only seems to happen with the prepackaged missions. Self-created missions don't have this problem, even with similar payloads and weight. Examples of missions where this happens are the ground attack instant action missions. I don't have this problem with any other modules. I have: Unchecked the option to synchronize HOTAs and in-game controls (I've actually never used this) Verified that I have no other inputs coming from other controllers. Properly, calibrated my throttle, stick and pedals. Any advice here ?

Thanks. I'll try to stick to the in-game setup. One observation, throttle seems to slide much more freely than any other throttle I've ever used. I mean no resistance at all is there. Is this normal ?

Mostly its the ministick that I find painful to use for the KA-50 or F15. I've had a few of the buttons get stuck in one position or the other and have to be replaced/repaired. Also having switches on the Warthog throttle make things painful at times when a simply button would suffice. Many of my issues can be addressed via Target, but I don't always have time to spending creating profiles. I think my feeling has always been that I loved the Joystick on this unit but enjoyed a Throttle like the X52 when flying everything except the A-10C. My guess is there are others that feel similarly as I noticed in the past couple of yrs TM have started selling the Warthog joystick standalone.

Hey All, After 2+ yrs of HOTAS Warthog ownership, I've never been very happy with the throttle. After much debate, I finally got the CH Pro Throttle which I'm planning to use for other aircraft apart from the A10c and pair it with the Warthog Stick I noticed that Wags uses this setup also. Is anyone else using this combination here ? Any thoughts or potential issues to be aware of ? Potential conflicts between TARGET and the CH Software ? I was planning to just start out using the in-game key mappings. Thanks!

Yes, i was trying to use the saitek profiler software but clearly that isnt an option wihtout the stick.

Does anyone know of a way to set a mode on the x52 pro throttle when the joystick is not connected ? I noticed that the commands I set in the Saitek profiler do not work and it is a result of not being able to set a mode on the throttle. See in the picture that none of the modes are available:

Looking to use TM Warthog joystick with the throttle from an X52 pro. I'm finding that the profile I set just does output any of the commands. It appears that this is because the throttle does not go into any of the 3 modes unless the Joystick is connected. I really have no desire to use the original joystick so I'm looking for solutions. As a side note, DCS does recognize most of the throttle inputs without the Saitek profiler running however there are some settings I want to use for slewing which don't seem to be possible for the ministick unless i use the Saitek profiler. Any way around this ?

I suppose you can get by without pedals for some aircraft using kybd, but for helicopters pedals are a must.

Another question. Is it normal for the throttle to show up in the windows controller GUI as an X/Y Axis instead of a slider ? My mini-stick also doesn't show up at all on this interface. Is this normal ?

Thanks for sharing this.I really do think I may have a hardware issue though. The stick still gives inputs i'm not quite expecting and while tweaking I just got a BSOD referencing a saitek driver. Not good. Been a disappointment thus far.

I got an x-55 a couple of days ago and had been testing a few profiles with the hope of using the ministick for slewing. I'm finding that the stick responds with erroneous Axis inputs. So for example I push up and it goes nowhere I push left and it goes down. I've double checked my mappings but this looks like a problem with the unit. Do you X-55 owners here even use the ministick ? What is everyone using for slewing if not ?

Thanks for sharing this. This helped me handle with the collective better. Still having a hard time hovering though. Just gotta keep at it I guess.

Here are my two attempts at hovering this evening. The curves that msalama posted helped alot. Thanks for that. Two questions: 1) Is it expected to be trimming during a maneuver like this ? I typically only use Trim during free flight or in preparation for a hover. I cant imagine timing while making these small adjustments with the cyclic. 2) What is the consensus on Rudder trimming ? I have it disabled as I'm used to the KA-50 which doesn't even have the option for rudder trimming. Hover1.trk Hover2.trk

I will try to post a track illustrating the areas where I'm struggling. Can you gents suggest curvature or saturation settings based on this new FM for me ?

Just starting flying the Huey a few days ago. However I'm seeing some differences in the way this machine acts during my attempts at hover compared to what is described in the training videos. I see some threads talking about tweaks to the FM however a lot of the helpful threads I've found are dated 2013. I'm seeing 3 major differences so far: 1) I'm requiring much more collective to get off the ground. The training videos are showing 30-40% collective on the control display but I'm having to put 70-80%. 2) Over sensitive collective is another issue I'm seeing. I'm finding that very slight adjustments of the collective leaves me ballooning upward or descending way too quickly. I've tried tweaking my axis settings but still thinking something isn't quite right. The sensitivity here seems far too much. 3) Do the the stick and rudder needed to be moved away from central positions for takeoff/hover. I find myself drifting a lot to the left whenever I do this. Is this still applicable also ? To be clear, I'm using a TM Warthog and have a few hundred hours (not recently though) with the Ka-50. I know this is a different machine but I'm having a hard time just doing the simplest things here and I can handle the Ka-50 quite well.

I made the changes u suggested with full screen disabled and water and shadows at low. I see only small improvement though. To be clear, I just played push 6-1 and spent most of the time between 10 and 19 fps. The misson starts off mid 30s but once the battle starts its a slideshow at times.

So I am still getting low fps after updating to the 14.4 drivers in many missons. For example, I just did push 6-1 and spent most of my time in the mid to low teens. Here is my current monitor config and graphics settings. Thoughts ? _ = function(p) return p; end; name = _('Widescreen + 1'); Description = 'Widescreen + 1' Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 1.77777; } } Shkval = --Shkval { x = 2560; y = 0; width = 900; height = 700; } ABRIS = --Abris { x = 3276; y = 0; width = 400; height = 700; } LEFT_MFCD = { x = 2560; y = 100; width = 650; height = 650; } RIGHT_MFCD = { x = 3276; y = 100; width = 650; height = 650; } Gui = { x = 0; y = 0; width = 2560; height = 1440; } UIMainView = Gui

Lovely. My thread has now been moved to a forum that has not had a new post in 2 weeks. Perhaps it would have been better to close it.

I actually tried the 14.4 drivers you suggested and it seems a little better but I will need to do a bit more testing. My card is totally stock haven't OC it one bit. Is the current DCS engine more dependent on CPU or GPU power ? My GFX settings are below.

Hi All, After running Eyefinity for a couple of years I'm looking to switch back to 1 large screen and second screen for mfd export. I recently got a 2560 x 1440 widescreen with a second 1366 x 768 screen for mfds but the FPS was poor. In some missions I got mid to low teens and single digits in others usually during battles things get bad. I usually play with heat blur off and medium water. Everything else is at max and I usually run the game in Fullscreen mode. My CPU is a circa 2008/09 CORE i7 920 that's overclocked to 3.8 GHZ and a Radeon 7950. I feel this machine should handle the resolution I'm trying to run here but am being proved otherwise. I'm looking to gauge the feelings of those here running multi-screen setups and set my expectations. I really am not looking to upgrade CPU/MB just yet but am open to any tweaks that can be suggested to make the frame rate acceptable.