TRZ06

The problem we are facing in todays gaming/sim world, is the technology/hardware is so good and fast, that to make a truly stunning, detailed game, takes a lot of time and overhead. It is a big gamble to put all the R&D money into a product without some financial backing and not know if it is going to turn a profit. IMO, the best game potential come from those who's motivations are not profit, but passion damning the costs. Not likely.

I would gladly pay $100 for a full DSC version of FC 2.0 The fighter sim industry is very much a niche market. We have to support the efforts of the few who still contribute to it. Kind of like what AOPA is to general aviation. You need your support group.

After spending about 2 hours on FC 2.0, I am glad to contribute $30. It looks great, HUGE improvement over LOMAC and FC 1.12. Best of all, no more crashes!!! I like the new "head tilting" while banking effect, in addition to the stock cockpit movement while maneuvering. Nice added effect. Love the new look, music. It is just very much more fluid all around, from UI to flying. GREAT JOB GUYS!!!!

I have done all that stuff, and mine still locks up. I can not fault anyone since Win 7 was not released when FC was put out. Having said that, when FC 2.0 comes out it better be fully compatible with Win 7 64bit.

MS Flight Sim X, is best used for "real" flying. When I was working on my instrument rating, using the G1000 in the 172SP to practice approaches saved me a lot of money. You can practice DME Arcs, ILS, VOR, GPS approaches all day long. I am now using it in multiplayer mode for my CFI training with my Dad to practice teaching a student how to fly. It is awesome we both can fly the same airplane and with Skype, I can talk to him as a real student and if needed take the controls as a real CFI would. It is a great investment for saving lots of money for "real" flight training in the real world.

Maybe it has been answered before, but will all flyable airplanes have the high fidelity flight characteristics like the SU25T? Also, will all aircraft have tires that will blowup if you apply the brakes too long and slip and slide across the runway? I tried the SU25T today for the first time since having CF, and I had the brakes on when landing and I started to slide, and I was like WTF, so I went to outside view and saw that the tires had blown and I was sliding on the rims WAY COOL!!!, I was seriously LOL. I also noticed that the SU25T handles more like a real airplane, in that if you try to turn with just ailerons without rudder input you get adverse yaw. The stall/spin characteristics were also more realistic. Please tell me all aircraft will behave in more of this high fidelity manner on FC 2.0???

With the high level of attention to detail and the amount of work and effort that goes into producing a specialized project like this, how is DCS able to fund such R&D?

I think it raised a good point. If you are married, it has to mean a little less dedication to your hard-core sim time. Me, I am married and with a 4YO, now that is really hard to balance if you add gaming time in. Plus I am working on my CFI. I have a hard time deciding whether to play FC and pull some g's and shoot at things, or shoot some approaches and practice my commercial maneuvers in MS Flight Sim X.

What I would really like to see (unfortunately probably not realistic) is a complete ground-up Military combat flight sim using todays technology. Look at what LOMAC was able to do 10 years ago, imagine what can be created today with a complete ground-up built combat flight sim. I remember back in the late 80s, early 90's , a new flight sim was created almost every year. Remember some of the classics: Jane's F18, Top Gun, F22 Stealth Fighter, etc, etc, etc. There has not been a new ground-up flight sim introduced in a long time. I guess playing the devil's avocate, with all the technology and what is capable today, it would take too much upfront money to produce a model ground-up combat flight sim and it would probably have to be priced out of reach for many to purchase it to recoup the R&D and make a profit. Too bad because with today's technology, it could really be something else.

I think the FM is decent considering this game was originally created almost 10 years ago. What I really want to see (and this has plaged LOMAC from the beginning) is less bugs, things to work as advertised, basic attention to detail. Better frame rates, less crashes, because what is the point if after investing 30 mins of your time, to have it all end with a game freeze or crash. I would also like to see better graphics with more detail, including better weather to take advantage of todays new systems and graphic cards. The core sim itself is really, really good, but it really needs to work better and not be buggy to be worth the time investment.

OK, I cleared the temp file and ran the program and it crashed again. Below are the 3 errors that were created in the TEMP file: Input focus: true DirectInput8Create() DirectInput8->EnumDevices() Input device found: Mouse Instance: 9421---1--668800 ProductName: Mouse Product: 9421---1--668800 Type: A mouse or mouse-like device (such as a trackball). Subtype: Subtype could not be determined. Detected: 5 buttons, 3 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Mouse added to list Using mouse elements: 5 buttons, 3 axes Input device found: Keyboard Instance: 9421---1--668800 ProductName: Keyboard Product: 9421---1--668800 Type: Keyboard or keyboard-like device. Subtype: IBM PC Enhanced 101/102-key or Microsoft Natural® keyboard. Detected: 128 buttons, 0 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Keyboard added to list Input device found: Saitek X52 Pro Flight Controller Instance: ----41-1-1668800 ProductName: Saitek X52 Pro Flight Controller Product: -697000000876876 Type: First-person action game device. Subtype: Device with six degrees of freedom; that is, three lateral axes and three rotational axes. Detected: 39 buttons, 9 axes, 1 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Joystick added to list Found joystick element: Y Axis Smoother created: Y Smoother y 4 Found joystick element: X Axis Smoother created: X Smoother x 0 Found joystick element: Z Rotation Smoother created: rZ Smoother rz 20 Found joystick element: Slider Smoother created: S Smoother slider 24 Found joystick element: Y Rotation Smoother created: rY Smoother ry 16 Found joystick element: X Rotation Smoother created: rX Smoother rx 12 Found joystick element: Z Axis Smoother created: Z Smoother z 8 Found joystick element: Button 0 Found joystick element: Button 1 Found joystick element: Button 2 Found joystick element: Button 3 Found joystick element: Button 4 Found joystick element: Button 5 Found joystick element: Button 6 Found joystick element: Button 7 Found joystick element: Button 8 Found joystick element: Button 9 Found joystick element: Button 10 Found joystick element: Button 11 Found joystick element: Button 12 Found joystick element: Button 13 Found joystick element: Button 14 Found joystick element: Button 15 Found joystick element: Button 16 Found joystick element: Button 17 Found joystick element: Button 18 Found joystick element: Button 19 Found joystick element: Button 20 Found joystick element: Button 21 Found joystick element: Button 22 Found joystick element: Button 23 Found joystick element: Button 24 Found joystick element: Button 25 Found joystick element: Button 26 Found joystick element: Button 27 Found joystick element: Button 28 Found joystick element: Button 29 Found joystick element: Button 30 Found joystick element: Button 31 Found joystick element: Button 32 Found joystick element: Button 33 Found joystick element: Button 34 Found joystick element: Button 35 Found joystick element: Button 36 Found joystick element: Button 37 Found joystick element: Button 38 Found joystick element: Hat Switch Found joystick element: Move Up/Down GUID_Unknown detected Found joystick element: Move Right/Left GUID_Unknown detected Found joystick element: Collection 0 - Joystick GUID_Unknown detected Found joystick element: Collection 1 - Pointer GUID_Unknown detected Using joystick elements: 39 buttons, 7 axes, 1 povs Input device found: HID-compliant consumer control device Instance: 423-91-1-2668800 ProductName: HID-compliant consumer control device Product: 5110000000876876 Type: Device that does not fall into another category. Detected: 573 buttons, 0 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. Input device found: HID-compliant device Instance: 9-3-91-1-3668800 ProductName: HID-compliant device Product: 5110000000876876 Type: Device that does not fall into another category. Detected: 3 buttons, 0 axes, 0 povs DIDC_ATTACHED: The device is physically attached. DIDC_EMULATED: If this flag is set, the data is coming from a user mode device interface, such as a Human Interface Device (HID), or by some other ring 3 means. If it is not set, the data is coming directly from a kernel mode driver. SoundManager: Starting... SoundManager: DirectSoundEnumerate DXMixer Primary Sound Driver : Starting... DXMixer Primary Sound Driver : Start succeeded DXMixer Speakers (Realtek High Definition Audio) : Starting... DXMixer Speakers (Realtek High Definition Audio) : Start succeeded DXMixer Digital Output(RCA+Optical) (Realtek High Definition Audio) : Starting... DXMixer Digital Output(RCA+Optical) (Realtek High Definition Audio) : Start succeeded DXMixer Realtek Digital Output (Realtek High Definition Audio) : Starting... DXMixer Realtek Digital Output (Realtek High Definition Audio) : Start succeeded SoundManager: DirectSoundCaptureEnumerate DXCapturer Primary Sound Capture Driver : Starting... DXCapturer Primary Sound Capture Driver : Start succeeded DXCapturer Microphone (Realtek High Definition Audio) : Starting... DXCapturer Microphone (Realtek High Definition Audio) : Start succeeded SoundManager: Start succeeded Sound Card Information: 100 Minimum sample rate specifications that are supported by this device's hardware secondary sound buffers. 200000 Maximum sample rate specifications that are supported by this device's hardware secondary sound buffers. 1 Number of buffers that can be mixed in hardware. This member can be less than the sum of dwMaxHwMixingStaticBuffers and dwMaxHwMixingStreamingBuffers. Resource tradeoffs frequently occur. 1 Maximum number of static buffers. 1 Maximum number of streaming sound buffers. 0 Number of unallocated buffers. On WDM drivers, this includes dwFreeHw3DAllBuffers. 0 Number of unallocated static buffers. 0 Number of unallocated streaming buffers. 0 Maximum number of 3-D buffers. 0 Maximum number of static 3-D buffers. 0 Maximum number of streaming 3-D buffers. 0 Number of unallocated 3-D buffers. 0 Number of unallocated static 3-D buffers. 0 Number of unallocated streaming 3-D buffers. 0 Size, in bytes, of the amount of memory on the sound card that stores static sound buffers. 0 Size, in bytes, of the free memory on the sound card. 0 Size, in bytes, of the largest contiguous block of free memory on the sound card. Catch: C:\LockOn\Projects\Sound\Source\IWaveIFileCreate.cpp 68 Catch: C:\LockOn\Projects\Operator\Source\ActionSystem.cpp 101 1/31/2010 14:27 Command Line : ActionProcessor::Reinitialize ActionProcessor::Reinitialize ActionProcessor::Reinitialize 1/31/2010 14:27 V512091930 Dispatcher: track version = 512091930 Dispatcher: initial random seed = 6872933 Dispatcher: apply random seed = 6872933 Cosmos: Mission date assigned - Year:2004, Month:6, Day:22 DXDefTexture: failed to load samara-red.bmp, D3DXERR_INVALIDDATA. DXDefTexture: failed to load samara-blue.bmp, D3DXERR_INVALIDDATA. DXDefTexture: failed to load samara-cherry.bmp, D3DXERR_INVALIDDATA. Warning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported. Missed description for USA in the FUI/EnglishVersion/Common.cfg Missed description for F_MINUS__ONE__FIVE_C in the FUI/EnglishVersion/Common.cfg Missed description for Crash in the FUI/EnglishVersion/Common.cfg Dispatcher: track version = 512091930 Dispatcher: initial random seed = 6984820 Dispatcher: apply random seed = 6984820 Cosmos: Mission date assigned - Year:2004, Month:6, Day:22 Warning: (texture class Graphics::DXFontTexture) must be loaded to step 1, step 0 reported. Warning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported. Warning: (effect class Graphics::DXProjLight) must be loaded to step 1, step 0 reported. Warning: (effect class Graphics::DXProjLight) must be loaded to step 2, step 1 reported. Missed description for Ukraine in the FUI/EnglishVersion/Common.cfg Missed description for Su_MINUS__TWO__SEVEN_ in the FUI/EnglishVersion/Common.cfg Missed description for Fire in the FUI/EnglishVersion/Common.cfg Missed description for Ejection in the FUI/EnglishVersion/Common.cfg Missed description for Landing in the FUI/EnglishVersion/Common.cfg Missed description for Random in the FUI/EnglishVersion/Common.cfg Missed description for Dzhankoy in the FUI/EnglishVersion/Common.cfg Dispatcher: track version = 512091930 Dispatcher: initial random seed = 7692433 Dispatcher: apply random seed = 7692433 Cosmos: Mission date assigned - Year:2004, Month:6, Day:22 Warning: (texture class Graphics::DXFontTexture) must be loaded to step 1, step 0 reported. Warning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported. Warning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported. Anybody know what the heck all that means? Thanks

I am having the same issue. It runs awesome for the few minutes that it runs, then it quits. I also notice that at about 3,000ft AGL and below the Altitude tape on the HUD goes wild while performing a steep bank in either direction. As a side note I was running 1.0 stock CD version fine with no crashes before buying and installing FC. I never playing FC1.1, as right after I purchased FC, I downloaded the 1.12 patch. I purchased FC via the website.