Mugenjin

That you purchased the notebook especially for flight simulation doesn't change the fact, that the video card is dated and is performance wise really low-end. If your CPU was around 40%, it means that something else is the bottleneck. Which kinda only leaves the GPU. When you're comparing visual fidelity, try F-15 quickstart with max and min settings. Since the flightdeck looks kinda bad on max settings too ^^ Posting screenshots might work as well.

Pff, also wenn es nicht zeitaufwändig/kostenintensiv gewesen wäre, hätte ED es doch gemacht. Haste nicht verstanden worauf ich hinauswollte? Außerdem hätte man es dann auch noch in andere Sprachen wie Französisch/Spanisch übersetzen müssen, was den Aufwand alles andere als verringert... Und eine deutsche Lokalisation war von Anfang nicht geplant, das was du in FC 2.0 Ordner gefunden hast, hat mit der Mig-29G zutun.

Well comparing with LOMAC is not helping since FC 2.0 is obviously different, i.e. more graphically demanding. We all know FC/DCS is more demanding on the CPU, but it's not like the GPU isn't needed at all. And a 8400M GS is an incredibly slow card I'm afraid. Especially the mobile version. Also on which resolution are you running FC?

Naja, in dem Fall müsste Woodstock ja nicht viel anbieten, da du ja meinst, dass ;)

it's gone.

You get less activations/deactivations depending on how many he's used.

yeeah right T-50 ^^

Cockpit display resolution: 512 Scenes: high Visibiliy: high Shadows: full AA/AF video card settings: 4X/4X Mirrors off, Win7-64bi From 60fps to 20fps makes the T-Frog unplayable for me T_T I barely notice the drop in the A-10 with Mavs though.

Wait until the c-17 has reached the parkbox to be safe. I did get the message as well, when I left as the c-17 touched the ground, but went home anyway. Upon landing I did get the mission completed message.

LOPE doesn't work since there is no meinit.xml anymore in FC2.0/DCS

No need to trim F-15 though :P I use a coolie for trim and rather have the rotaries for radar horizontal/vertical/targetbox/mfd.

Just rotate the rotaries while the window to assign a key is open and it'll automatically detect it. As for the key map I don't think that there is one yet. Use this as a reference to find out which keys are meant.

Are you sure you clicked the field under the joystick COLOUMN to bind your joystick-key to?

Cleared the whole keyboard coloumn? xD

Kann man nciht viel machen, außer Cockpit display resolution auf 256 stellen.

\Lock On Flaming Cliffs 2.0\Config\Weapons\aircraft_gun_mounts.lua change "shells = shell_ref("GAU8_30_AP")" to e.g. "shells = shell_ref("2A42_30_HE")" That's no HEI though and you can't reeally penetrate armored targets.

btw that's not the mini HUD. I'm not sure but isn't this the game avionisc thing? The mini HUD allows you to see the HUD while looking to the side/up/wherever.

There are only a few which totally changed (waypoints, bugging targets, release weapons, a couple more). But there are a lot of changes to some key commands which now use a specific side of a key, i.e. left or right ctrl. You'll need to make quite some adjustments, but it shouldn't take that long. In fact it'll be faster than programming the whole shebang for every single aircraft. Did the same with my sst profile and it's a lot easier imho (and I can use advanced commands)

modman will do that automatically

optimist. :smilewink:

Because the gauge's scale is in kg... Dunno what Vekkinho was going for, but 3500kg for Mig-29s is spot on/some 3200kg for the Mig-29a.

Are you positive every piece of your hardware is working properly? i.e. gpu/cpu/memory stress test while monitoring temps?

Would you mind translating? Not all of us can read/understand that :P

less barrel wear? :P

Rate of fire toggle is also gone from the F-15. I don't miss em anyway.