Slayer

I doubt the Russian GLASNOS and INS cordinates match up to the US systems.

It's an Nvidia driver problem as I posted above. There is no distinction between executables with with the same name. I believe the profiles are embeded within Windows registry so it's not an easy fix unless you custom modify or delete the profiles with a tool like nhancer or name the .exe to something that the Nvidia driver doesnt recognise. I think the ez fix is to temporarily rename the .exe (untested)

goes in: C:\Program Files\Eagle Dynamics\DCS A-10C Beta\Training\en\Aircraft Operation\1 folder ...or wherever it is on your HD rename to same as the file in there.

Nvidia driver profiles-game detected as Blackshark The Nvidia driver is detecting DCS:A10C(32 & 64 ) as DCS:Blackshark and using those settings. Cannot delete the profile because it is integrated into the driver. I think its because the driver only looks for DCS.exe running and doesn't do a version check or anything. Not sure what driver level fixes Nvidia may have done for Blackshark but I would guess that they are not applicable to A10C ? I restored the profile to default so as not to cause instability until I can see what effect they have. Note: When the DCS:Blackshark .exe was renamed to simulator.exe in the 1.02 patch the driver started using the same settings as FC2 since they both now have the same name. The driver level fixes that are being used are for DCS:BLackshark 1.0 Very confusing. Not sure how to fix unless each game has a different .exe name or Nvidia's driver does a better detection method to distinguish between programs...

In the startup tutorial there was 1 cloud that was flickering. I pan around the whole area and it is the only cloud flickering. It looked exactly like the cloud flickering problem in LOFC except only the single cloud. Reloaded the game and it went away. I wanted to FRAPS it but haven't been able to reproduce it yet. Hardware config is in my sig. This was with the 32bit exe on Windows 7x64. Everything set to high 1920x1200 resolution.

I hope so....I'm sure A10 will be amazing but DCS:BS will be on my harddrive for years. Maybee I will unistall if there is a DCS:AH-64 but thats all still up in the air. Theres just some things the shark can do that a fastmover can't.

I think cows is at 4:20 or so 7:34 8:20 and 8:48 there are people running away but someone did a bad edit job at masking them out. I cant find the other one again and don't want to keep watching it over and over

I saw at least 4 times in those "cleared hot" video clips ground troops running away. Not including the gun run on the cows lol.

Every DX11 game I own(Dirt2, Metro2033, STALKER, BF2BC) supports multiple version of DX hardware its not DX11 or bust.........You don't have to buy new hardware unless you want to have better graphics....so stop trying to portray it as a all or nothing affair ...it's not. How many DX11 games do you own and what do you base your assumptions on? My guess would be zero.

I have a 900watt PSU and have them plugged into my monitor which has a self powered USB 2.0 hub. The cords are too short to plug into the back of the PC. Device manager says each hub port has 500 miliamps available. maybe I'll have to get some extensions and try different ports on the back of the PC. USB 2.0 is supposed to have more power available thats why I'm stumped......

Anyone else having an issue where the MFD's turn off then back on? They are disconnecting from the USB because I can hear the the USB plugin sound from Windows when I'm in a game. This happens even when I'm just on the desktop doing nothing. No rime or reason just randomly turns either one off then back on. I tried disabling the " allow windows to put to sleep to conserve power" option in device manager for the hub they are attached to and also checked the power draw on the USB hub in device manager and they are not over the limit (powered hub) I read of other users with this problem and TM tech support is useless.....

Please make a video. It would be nice to see the problem from your perspective.

Direct Compute for DirectX11 would offload this on the graphics card instead of on the CPU so the wasted CPU cycles argument doesn't hold water. "Microsoft’s DirectCompute is a new GPU Computing API that runs on NVIDIA’s current CUDA architecture under both Windows VISTA and Windows 7. DirectCompute is supported on current DX10 class GPU’s and future DX11 GPU’s. It allows developers to harness the massive parallel computing power of NVIDIA GPU’s to create compelling computing applications in consumer and professional markets. " Too bad they decided to scrap DX11 for DCS:WH

Bucic Have you tried holding down the trim a little bit longer? I remember another thread where the guy was releasing trim too fast and it was causing a similar issue to what you describe. Also do you manouver with the trim button held down or do you trim-move-trim-move. I find holding the trim button down then releasing it after you have it set where you want to be a much better method(for me anyways)

Everyone here seems to be equating the ragdoll physics with just blowing up infantry and watching them flailing through the air. I'm not sure what the OP had in mind here but whatever you call it the way it stands now you may as well be shooting at paper cutouts. It's not a waste of time to animate infantry movement. After you play the game for a few weeks and get your head around all the flight model and controls it becomes somewhat booring to shoot at the same targets. You know exactly where they will be and they will just sit there whilst you rain death and destruction down on them. Not very realistic at all. At least in ARMA when the AI sees bullets hitting the ground near them they react and start going for cover and going prone and looking for you. Granted the AI in that series is terrible too but at least they do SOMETHING. It's never the exact same mission twice because they don't always act the same.

Did you try to increase the time? I watched your tracks and it doesnt appear the joystick is spiking or anything weird that would prevent it from registering the center position. Q: For non-FF sticks, is it possible to increase the time provided to neutralize the joystick after trimming the helicopter (i.e. the time between releasing the trim button and the trim setting taking effect)? A: Yes. Open the following file: \...\Scripts\Aircrafts\Ka-50\FMOptions.lua. Look for the following line: “TrimmerTauInverse”. The lower this number, the longer the trim setting delay. Warning! Altering this value will likely result in a failure to reproduce track recordings accurately when they include a player-controlled helicopter.

There is no way to unlink the pedals from the trim system that I'm aware of. It would be nice to be able to do so considering there are no FFB pedals (other than homebrew)

Having to recenter the pedals in the game while having a FFB stick is hard to get used to since you dont recenter the stick. I would mod my pedals in a sec to hold position if it would work like that in the game :/ Seems all you would need are a few cheapo hydraulic dampers and to just adjust the pedals so there is no centering spring...but then this would make the pedals terrible for fast movers since the pedals would no longer return to center.

I'd rather have it. The A10 is mostly being used to attack men on the ground these days anyways. Infantry is the biggest part of any war. You can bomb and strafe everything til your hearts content but you cant win a war unless theres troops on the ground where the meat meets the metal. I'm sorry I don't agree at all with the yesmen I want to see troops fleeing and acting in a somewhat realistic manner. No we don't need little exploding bits of men, but having ground troops that actually move and participate would be ideal.

It has been a while since I did a new skin, but I'm pretty sure you need a new CLSID if you create a new skin (do not need to do this if you edit an existing skin). I believe option 4 is the only one that works. All the other stuff is for Windows/Registry etc.

FF is nice but a huge learning curve again. By the time I learn enough to actually fly a whole mission and get my controls set up properly A10C will come out :/ . It is a great mod of one of the best sims ever. Heck at this point it's really a new game more than a mod. So many good looking sims on the horizon for next year it's starting to remind me of the late 90's / early 2000's again :P. I bet I've owned every flight sim there was from that period. It's just hard to devote the time required to learn this knowing I will be setting it aside the second A10C hits.....

People who aren't hardcore flightsim gearheads with boatloads of money...... Thats the problem with FSX and flight simulator in general. You can spend over a thousand dollars just to make your sim look good and realistic. They put out minimal features and a framework of a sim. I predict that MS Flight will be more of the same with LIVE rammed down your throat and dummied down for XBOX users. I personnally hate LIVE it's like xbox for PC. Who wants that for a flight sim? Youll have to buy microsoft points to spend on aircraft then they will deny you tech support because you didnt "pay " for your product you bought points that some lawyer devised a way of bilking you out of your money so that you have no legal recourse. They will loose a lot of developers. Probably a lot will shift towards Xplane...

You might want to also check that your "power management" setting in your profile is set to "prefer maximum performance" instead of "adaptive"

My motherboard didn't properly support GTX470's and 480's. I believe there was an issue with some new ATI cards as well. I had to update to a newer BIOS. I would check for a BIOS update and check into the support forums for your motherboard manufacturer and see if other people are having similar issues. Also if you are going from an old NVIDIA card like an 8800 to a newer one you should completely uninstall the old drivers, even if you already had the latest drivers. If you don't sometimes strange things happen... The newewst Nvidia beta driver now has an option to completely clear and uninstall old drivers too...really liking it.

I've just downloaded and installed the new drivers(get them from the beta section). I almost wet myself the game was working fine on my brand new 480 GTX SLI setup. No weirdness or crashes or anything. The fix wasnt specifically for FreeFalcon, it was for AF. So you just have to rename your FFViper.exe to FalconAF.exe and it will work. THis will fake the Nvidia driver into thinking its AF and apply the DirectX 7 driver level fixes. I'm using Windows 7 x64. It's the first time I have ever been able to run this game outside of forcing it to window mode. Some users over at the FF board are supposedly petitioning Nvidia to put a profile in the driver for FF so hopefully they listen.