joker68

Hi Konrad. No, I didn't map the elevator trim to a slider (but this may be a better idea than using the HAT that warthog has for this purpose). I use a set of old TM Elite rudders. They work "ok" with most sims, but they really lack "precision", because they are connected thru a serial-to-usb adapter, and they behave like they have only 8 pre-programmed positions for each side (if you look them closely on the game, they seem to move at small increments or "micro-jumps" each time, so it seems that my serial-to-usb converter is making some math to convert the signals from analog to digital, which causes this loss of precision). At most sims, including RoF which uses rudder A LOT, this isn't a concern, but maybe in the P51 this become a major issue due to hyper sensitivity of the plane to the minimum input. About using the rudder, I'm sure using it a lot in the P51. :) It's like you said, a dance. The only way I found to keep it at "the edge" on a steep curve at maximum G sustainable. It is very rewarding to fly the P51, only if I could manage to shot down that bogey... :music_whistling:

Hm, no. The mission starts with the Mustang already in the air, with the enemy doing a fast front pass at my right side, so I think it's "all set" for a dogfight already, but I'll check. Maybe that's the "trick" that I'm missing. (I'm pretty new to the P51 sim). Well, I think that P51 doesn't care about what kind of joystick you use, unlike A10-C, which will recognize and "auto-set" automatically for Warthog. I did try the flaps, and they surely help sustaining the curve, but they did very little about how many G's I was able to pull before the aircraft spins. I am on the same path: "keep trying, keep training", but without being able to pull more than 4.8~5G at 300mph at sea level, there's not much I can do against the AI enemy on a dogfight. He climbs, accelerates and turns (way) better than me. My hopes are on the trimming system, and "keep trying". Must be me, because other systems in the game are working 100%, so I assume there's nothing wrong with my install. Strange that this is the first time I *really* have a hard time flying a sim (I fly sims for more than 20 years - my first one was on a PC 8Mhz, in the Mesozoic Era!) :) Thanks for all the inputs. Cheers.

@Nate: Thanks for the tips, will try and see if I can improve. Will report back. EDIT: (reporting back): well, using a curve of 30 improved a little, but in fact I'm maskerading the real problem: at 300mph at sea level the plane spins/stalls when I reach (near) 5G! The plane is behaving like I was at 30K feet or so. Now I know why AI is able to do those UFO maneuvers: it must be pulling 6G+ (which is perfectly possible according to the graph at page 103 of the Flight Manual (full). I am seeing this while flying the quick mission "Dogfight P51 vs P51". Anyone else can confirm this? (5G at sea level). Tried with and without flaps. @jcomm: Well, there is no update (at least that I know of) for Win8. I'm just using the Win7 drivers, and they seem to be working fine (RoF, A-10C, Falcon BMS). I usually play "barebones", without TARGET.

Hi guys. (Re) installed DCS today on a Win8 rig. So far, so good. After setting the axis, I went to a quick flight with the P-51, but hey, I am not allowed to move the stick more than an inch off center. The plane automatically enters a spin or start to buffet really hard. This happens in any speed (fast, slow, doesn't matter). Worst, the other mustang (AI) is literally doing barrel rolls around me in the meantime. My stick (Warthog) is perfectly calibrated. I can confirm this inside the DCS game looking at the controls. Pedals are calibrated too. I don't know what I'm doing wrong. I just can't make a hard turn (or a turn by all means) with this bird, but the AI seems to be playing IL-2 1946!! I would have more chances dogfighting in a C-130! :joystick: Any hint? A10 seems to be working fine. Note: I've just flown a couple quick missions before in P51 (old Win7 rig, ground attack only). First time trying to dogfight and make curves without bombs under wings.

Hi, I've downloaded a mod for A10C (http://files.digitalcombatsimulator.com/en/111154/) that enhances the immersion by replacing the static.ogg file with a real conversation between pilots. Problem: in my game, it plays a little bit too quiet. :( I've tried to raise it's volume through a sound editor, but even then, with the radio volume set to max inside the game, I can barely hear the conversation over other plane sounds. Is there a way to tweak the sounds in A10C (perhaps editing some lua file to tell it to play static.ogg louder)? Thanks EDIT: Done. Went ahead and *quadrupled* the volume inside the file. Just doubling it didn't make a difference inside the game (although I could notice the diff on windows player).

+1 for more WWII planes. ClOD is broken, at this pace it will take at least 12 or more months until they have something barely usable.

Win7 32bit. Using "external" mode, on second display. When mission is loading, there is a gray window saying "www<dot>kegetys<dot>net" in the upper left. After the mission begins, the window stays gray, showing nothing, no matter what kind of weapon I select. Tried to change the folder where d3d9 and ilj5 dlls are located, changing from "auto" to that "<folder path>" with and without quotes, (even maintaining copies of them in the original places), but then the window wouldn't even appear and/or the mission would go straight to the "end of mission" screen after loading. :huh: *EDIT* Forgot to mention, running FC2 1.2.1 vanilla.

Installed the driver version 10.5 and the shimmering is gone! YAY!

Nevermind, got the 10.5 drivers and the shimmering is gone. Since this is my first ATI, I almost sent it back... guess the drivers aren't so good as nVidias... let's hope 10.7 gets better. :)

Thanks slug88, but unfortunately it doesn't help with the citie's shimmering. It helps with the flickering at the mountains (wich I had in BS). I don't know what to do... I guess I will need to try every single ATI driver out there to see if this problem is 10.6 related. Do you use an ATI card? If so, if you don't have this problem with cities, can you tell me which driver version are you using? This is my first ATI card, so I'm pretty noob about ATI driver issues...

Thanks luckybob9, but unfortunately that is not the case. I've already tried that. This mod seems to solve the "mountain flickering" problem. Unfortunately, it doesn't help with the cities looking like an ant's armada.

Please, can you point me what version did you use to solve that? I'm using the 10.6 and having A LOT of shimmering, driving me crazy to fix this. The card is brand new and this is the first ATI driver that I use (I was on nVidia before). Thanks.

This is happening to me using an HD5850 (bought 2 days ago, still no fun). I had an 9800GTX+ before, with no shimmering at all. Tried every possible combination in Catalyst 10.6... if you can point me some tips on making this ATI work without shimmering, I would appreciate. Missing my nVidia. :mad:

Same here. Tried every possible combination of AA and AF on Catalyst 10.6. Also tried other stuff like AI off/on, Vsync, etc. I'm beggining to think that I did a really bad move changing my old 9800GTX+ OC by this ATI. :mad: EDIT: version 10.5 solved the problem. 10.6 is buggy.

Try this: structures = {40, 4000}; trees = {1000, 6000}; dynamic = {300, 20000}; objects = {3000, 80000}; mirage = {3000, 20000}; surface = {14000, 80000}; lights = {100, 30000}; You can fiddle with structures values *(like structures = {60, 6000}) to see things like buildings and bridges farther away, but be advised that it can have a negative impact on the performance.

My version is a little different (came with "RivaTuner 2.24 MSI Master Overclocking Area 2009 edition"), but I think it must have the same behavior. And yes, it must be active during play. You don't need to create a special profile though, just use the "Global" like shown.

Only if you set it via nVidia or ATI panels. That's the very reason that D3D Overrider was born. It allows triple buffer in DX. "Triple buffering in drivers is only available for OpenGL. The D3D overrider is for forcing triple buffering in all direct3D games, by making a direct call on the api itself. This in turn prevents tearing on games when synced to your monitor refresh rate, very important if you use a TFT as they use a low refresh rate, as well as prone to tearing." excerpt from http://forums.guru3d.com/showthread.php?t=208499 "Bottom line , is that it keeps your frames from really bottoming out when V-synch is on." If you don't use vsync, I guess you'll see no difference.

Yes, it does force vsync (if you want to), but it also allows the triple buffering for DX (the main reason why I used it). For my old card, I've gained that much (I always use vsync, because I don't like tearing). Didn't tried without vsync, but I guess it would be better in terms of FPS. Before D3D, inside cockpit, going to port, I had 30 fps, now I have 45 in the same track. Maybe it doesn't make such a difference for more powerful cards? I don't remember changing anything else on nHancer or into the game. Also, I'm just using the "Global" profile. Trying to create a profile for simulator.exe resulted in micro stutter for me.

Hi people, Perhaps some of you may have heard about D3D Overrider, a little tool that comes with RivaTuner. It is capable of activating triple buffering for DX games (nvidia and ATI panels only do this for OpenGL games). Well, for me, this little gem is responsible for 10~15 fps gain!! Right now, I'm running a Q6600 @ 3Ghz on an old D975XBX "badaxe", WinXp 3Gb RAM, 9800GTX+ 512Mb, driver 197.13, everything on high (except shadows that I keep at all planar), blur on, traffic on, vsync on, forcing 4xS combined AA and 16xAF thru nHancer, and I'm having 40+ ~ 50+ fps 90% of the time, and during hot combat over cities dropping around 30+ fps. The mission that I use for benchmark is the "visit to port". I was about to purchase a new card (5850 1Gb), but now I'm happy! :) Hope this helps someone else. :pilotfly: Cheers JoKeR