aphill

Wow nobody having this problem?? I know a number of my squadmates are seeing this.

I made a smaller test mission. 2 of four rolled off to the right and missed. Also The camera image coming from the slammers are really awful is there something I can do to make it better? slam attack_sam 11_2.trk

Anybody have the problem of the slam er dropping a wingtip and veering of a locked target for no apparent reason? Happens near the end of the run. I have a track but its too big to attach, is there a way to edit it?

It just seems less accurate than it was a couple of patches ago. I may be wrong but I seem to get less kills than previously. Soom just flat miss. some explode close with no damage at all. Has something changed lately? Harms_Gulf 12422.trk

After latest patch harms are still highly inaccurate.

Same for me

I uninstalled and reinstalled OB and it fixed the problem.

Well that is interesting. I have no problem with the stable version it works like a champ. I did a repair on OB last night with no difference. I will do another repair and if that doesn't work I will uninstall and re install. It has to be a corrupted file I'm thinking.

I tried again using point track. As soon as the laser starts working (I pressed the weapon release button instead of the trigger) watch the left DDI and you will see the white box appear for less than a second and then disappear. I think I am getting the process right, but not positive. I will try the vanilla version instead of open beta the next try. laseing problem 2.trk

Thanks for the reply. The white box comes on and goes out fast so it is easy to miss. I will watch your track and do as you do, and see what happens.

Hi Guys I get the TP to lock a target the mavs lock on when I uncage them. The laser fires, but the filled box indicating the mavs are seeing the locked target comes on for about a second and then its back to an X. This is a recent development. It has not done before today actually. I am posting a track. Note how fast the white filled box disappears. Thanks for any help laseing problem.trk

FC 2 is installed. I cant seem to get things mapped to my CH throttle though. I set internal and external views to my CH throttle and the game doesn't recognize them. I also tried to map the zoom out low and zoom in slow to the throttle ( I did it under the CH throttle in game, the game is seeing the controllers it just doesn't save the changes or something) The controls seem to be very touchy, although they seem to work properly.

Thanks, I will give it a try.

Thanks for the reply EtherealN, Yes I was trying to get the vanilla version to work. I figured if that wouldn't work, then FC 2 night not. Sounds like from what you said that it may not be a problem. I was thinking in the input settings in game, I should have only the MSFFB 2stick and the CH throttle be the only controllers assigned the flight control function IE: no keyboard or throttle settings for aileron rudder and elevator. I thought I did that but maybe I missed something I will check that out. So, after I install the vanilla version, I should install FC 2 (no patches added to the vanilla) Is that correct? Thanks!

S! All, I know this is going to sound weird, but I have tried to figure it out myself, and no joy. So here is my problem. I have a control problem with loc on. It may be just a joystick problem, or more likely, an in game configuration problem, but the game is unplayable as it is. I am just trying to get the original game to run right before I get FC 2. So here is the problem, the controls, ailerons especially, flutter and are intermittent. I can start into a roll say to the right and before I can complete it, the ailerons hang up and sometimes just reverse themselves. If I rock the stick back the other way it will sometimes respond. I can be flying straight and level hands off the stick and all of a sudden the plane (A-10) will suddenly start into a roll, with no input from me. I am using a MSFFB 2 stick that works great with IL-2 and ROF and any other flight sim so I don’t think it’s the stick. Just to check that out, I switched to my CH stick and rudder pedals and the same thing happens. Visually in the cockpit view the stick will, with no input from me, wiggle back and forth and the ailerons will be doing the same. I hope I have made some sense but this is a weird problem I have never seen such a thing before. Has anyone had this sort of problem? And maybe help me out. I would really like to fly this sim. Thanks Here is some of my systems info System Information ------------------ Time of this report: 4/18/2010, 22:21:59 Machine name: STONEWALL Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.100216-1514) Language: English (Regional Setting: English) System Manufacturer: OEM System Model: OEM BIOS: Phoenix - AwardBIOS v6.00PG Processor: Intel® Core2 Duo CPU E8500 @ 3.16GHz (2 CPUs) Memory: 3326MB RAM Page File: 499MB used, 4711MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.2600.5512 32bit Unicode ------------ DxDiag Notes ------------ DirectX Files Tab: No problems found. Display Tab 1: No problems found. Sound Tab 1: No problems found. Music Tab: No problems found. Input Tab: No problems found. Network Tab: No problems found. --------------- Display Devices --------------- Card name: NVIDIA GeForce GTX 260 Manufacturer: NVIDIA Chip type: GeForce GTX 260 DAC type: Integrated RAMDAC Device Key: Enum\PCI\VEN_10DE&DEV_05E2&SUBSYS_064B10DE&REV_A1 Display Memory: 896.0 MB Current Mode: 1920 x 1200 (32 bit) (60Hz) Monitor: Plug and Play Monitor Monitor Max Res: 1600,1200 Driver Name: nv4_disp.dll Driver Version: 6.14.0011.9713 (English) DDI Version: 9 (or higher) Driver Attributes: Final Retail Driver Date/Size: 3/16/2010 02:51:59, 6432128 bytes WHQL Logo'd: Yes WHQL Date Stamp: n/a VDD: n/a