Jump to content

Recommended Posts

Posted

Thanks a lot Rakov, been banging my head against the wall for 2 days with the exact same problem as you, realise my usb pad adaptator for ps2 plugged in the front usb made the game crash at start, no problem after removal.

 

that adaptator only work in seven with artisanal vista drivers, maybe the problem come from that, your rudders are pretty old ? i d look there.

 

thanks again

Posted

In the hopes that this might help somehow, here's latest update from my experimentation.

 

After my initial problems (posted earlier in this thread), I reloaded Windows 7 Ultimate 64 bit. I only installed a usb corded mouse and keyboard in the back usb ports. These were not the same wireless keyboard and mouse I had been using when I first found this issue. I did not install a joystick, wheel, Track IR, or any of their associated software. In other words, the only peripherals plugged in to the computer were the mouse, keyboard, monitors, and speakers. I still had the same issues after the fresh OS install. In other words, neither Lock on 1.0 or Flaming Cliffs 1,12b would recognize the keyboard at all - i.e. no response from the keyboard in the input options screen, and Flaming Cliffs 2 showed the error that we have posted screenshots of earlier in this thread.

 

I then installed Windows 7 Ultimate 32-bit, and everything worked fine from the beginning. Joystick, keyboard, foot pedals etc. all working well just like in my XP 32-bit load on this same dual boot computer. No problems at all.

 

Unforunately, since I do a lot of modeling for Flaming CLiffs, I need the 64-bit OS so that I can use all my memory in 3DS Max. So for now, I will have to continue to model on XP 64-bit. The trouble with that is that I can't test the new mods on Windows 7 that most people are using now.

 

I hope this info will be of use so that I can get FC2 working on Windows 7 64-bit.

 

I assume some folks do have FC2 working on Windows 7 Ultimate 64-bit?

 

Thanks

Скрытый текст

 

data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==
data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==
data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==

 


 

 

 

Posted

Yes, FC2 and Windows 7 x64 is really to things that goes really well together. Yours truly doesn't anything else at the moment.

The mind is like a parachute. It only works when it's open | The important thing is not to stop questioning

Posted

I've just bought FC2, and I'm having a similiar problem. When I try to start up FC2 I get the same Flaming Cliffs 2.0-window, and the beginning on the background music. Takes a few seconds and then the whole window disappears.

 

Nothing is printed in errorlogs, and I've tried all the little tricks mentioned here, including new DX, switching USB devices and redownloading from a diffo source & reinstalling.

 

However, I get no runtime errors or anything, and my multiplayer.bat boots up fine.

Posted

I bought CH Pedals and my problems went away, so I won't be pursuing this thread... there shouldn't be "incompatible devices" in my opinion though.

Posted

Yeah, no proper display adapter (Direct3D missing!). Not going to work. You need to get a Dx9 card in there.

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...