driver7408

Bump. I wish to do the same thing. Tried keytweak program, and it's fine in windows, but disappears in BS. I have a small number pad which is easier to keep close by, and I would rather use it to do the voice commands. Trying to control the bird and hit f keys on the top of the keyboard is cumbersome. Only other option I can think of is voice buddy, but I'd assume that will probably slow down the processor a bit too much and tax frame rates. Any ideas?

Dead honest.. I did absolutely NOTHING different this install vs. the last install. Mind you, I'm running Microsoft Vista. I did find forum posts with this same issue, and reinstalling seemed to fix it; or I could assume it did because the OP's never explained anything else they found that fixed the problem. As far as my last rant: I posted an error log as requested, and never got any feedback. I think I later found on my own trial and error efforts that the newest version of track IR drivers didn't work right with LOMAC. My bad for trying to use the latest drivers on a game that was incompatible with them after their newest patch. Nice you're so quick to judge and assume. Maybe you need to read and comprehend my post history a little better before you start making personal judgements.

Wow. You obviously have a lot of time on your hands to read forum posts. I'm not asking for the developer to cater to my every need, just pay attention to issues and offer a forum where they can be fixed. (Gee, not yet I think I've found a post that even explains, solves or responds to the Microsoft FFB trim issue...Yet a million and one posts by people who don't even know what force trim is, when a little research would explain it quite well) Not yet sure if patch 1.02 fixed it, because it has yet to work. I think if you do a little more reading with all of that time you seem to have, you will find many others with the EXACT same complaints about software support here. PS: I reinstalled patch 1.02 EXACTLY the same way I did the first time, and now it works. Now tell me its something due to my setup.

Just installed 1.0 in C: aaa folder. Boots fine. works fine. No issues. Now gonna install the patch again and report back.

Upon opening BS: Error: .\blackshark\modules\me_traceback.lua:110:bad arguement #1 to 'member' (string expected,got no value) followed by a list of ->stack: lines Ive done a full search on this forum and found a couple similar problems, but no solutions (No old files in Virtual Store, running as admin, ect.) I also followed the 1.02 install guide to the letter. Patching a program shouldn't be this difficult. I update other software all the time without encountering these issues. Gonna try one more reinstall. If it doesn't work I'm done bothering with this program altogether.

I know all about patience and attack helicopters. I used to work on them. I uninstalled 1.01 and reinstalled the patch over a clean version of 1.0, based on my conclusions from the forum after a good hour of reading the 1.02 patch thread. I'm currently running a dual boot Vista 32/ XP 64 machine with an E8500 overclocked to around 4.1, 4 gigs RAM, and an 8800 ultra. I installed it on Vista 32. I've checked the basics. All settings are optimal; I built this computer to run FSX. BS ran just fine before the patch. The error shows up so far during launching BS 1.02, and when I go to the options screen (in attempts to set up my controller) The error is a long repeated list of string "expected got no value", referencing various lua/ me files. It pops up when I start the sim, and again when I hit the 'options' button. Only thing I did differently is I installed DCS:BS in a file I named "aaa" on my root hard drive, rather in the program files directory, and its likely trying to reference a folder somewhere else that isn't there. I have the feeling that if I reinstall it under program files, this fault will go away. I have read though that its better not to install BS under program files. I have looked forever on this forum for a good install guide/FAQ for advanced users. Someone really needs to write one. Most of what I have to read through are repeated posts from people with little computer / helicopter knowledge asking the same simple questions. It gets tiring scouring through 100's of threads just to get one good tidbit of useful info that applies to my installation.

String expected, got no value. stackback something or another. lua files. I have no patience for this. Version 1.01 worked just fine. I installed this patch fresh, from 1.0 disc. I think that the mods should organize this forum a little better with forum specific subheadings, especially for bugs. This is not a simple simulator, nor a simple helicopter, but at the same time Its just tiring scouring through post after post to get information here. I notice I spend more time doing that than I do playing. I don't even feel like looking around for what this issue could be.

Normally I'm an FSX fan, but I love this sim. I got into it a several months ago, but had to take a break, due to work (real life helo pilot.) My current system is a dual core E8500 running moderately overclocked with 4 gigs ram and an 8800 ultra. I'm running dual monitors (42' plasma and a 19' LCD.) I just came across the touchbuddy mod, and I just ordered a touchscreen overlay for my 19' monitor. I want to do a clean OS/DCS reinstall and incorporate the touchbuddy panels onto my 19' monitor so I can use it efficiently. (I think having all those panels right there at my fingertips would make the sim way more enjoyable.) I have a choice of operating systems: Vista 32, Vista 64, and XP 64. I would like to know which of these OS's would be the best for this particular application (dual monitor/touchbuddy) And also, should I install the DCS program files onto their own separate hard drive, and would there be any benefit to doing that, as I know there is for FSX.

I had this awesome flight once. Felt like I was getting hit repeatedly by artillery fire, but somehow, my tactical flying skills and clever use of flares was simply no match for the AI enemy. I ended up single handedly destroying 2 convoys in my 30 minute sortie. I later reviewed the track, After the first 2 minutes, I quickly realized I had been playing in "invincible" mode. :noexpression:

Input device found: USB Receiver Instance: 46--9--1-1668800 ProductName: USB Receiver Product: 142-000000876876 Type: Device that does not fall into another category. Detected: 652 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: USB Receiver Instance: -9--9--1-2668800 ProductName: USB Receiver Product: 142-000000876876 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. Input device found: USB Receiver Instance: 0-5-9--1-3668800 ProductName: USB Receiver Product: 142-000000876876 Type: Device that does not fall into another category. Detected: 0 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: USB Receiver Instance: 151-9--1-4668800 ProductName: USB Receiver Product: 142-000000876876 Type: Device that does not fall into another category. Detected: 0 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: CH PRO THROTTLE USB Instance: --550--1-2668800 ProductName: CH PRO THROTTLE USB Product: -6-0000000876876 Type: Joystick. Subtype: Standard joystick that provides the minimum number of device objects for action mapping. Detected: 19 buttons, 3 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: Z Axis Smoother created: Z Smoother z 8 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: Hat Switch 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: Collection 0 - Joystick GUID_Unknown detected Found joystick element: Collection 1 - Pointer GUID_Unknown detected Using joystick elements: 19 buttons, 3 axes, 1 povs Input device found: CH PRO PEDALS USB Instance: --550--1-3668800 ProductName: CH PRO PEDALS USB Product: -6-0000000876876 Type: Joystick. Subtype: Joystick that does not provide the minimum number of device objects for action mapping. Detected: 0 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. Joystick added to list Found joystick element: Z Axis Smoother created: Z Smoother z 8 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: Collection 0 - Joystick GUID_Unknown detected Found joystick element: Collection 1 - Pointer GUID_Unknown detected Using joystick elements: 0 buttons, 3 axes, 0 povs Input device found: Saitek Pro Flight Yoke Instance: 8-6-8--1-1668800 ProductName: Saitek Pro Flight Yoke Product: -6-1000000876876 Type: Joystick. Subtype: Standard joystick that provides the minimum number of device objects for action mapping. Detected: 23 buttons, 5 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: 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: Hat Switch 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: Collection 0 - Joystick GUID_Unknown detected Found joystick element: Collection 1 GUID_Unknown detected Using joystick elements: 23 buttons, 5 axes, 1 povs Input device found: Saitek Pro Flight Quadrant Instance: ---2---1-1668800 ProductName: Saitek Pro Flight Quadrant Product: -641000000876876 Type: Joystick. Subtype: Joystick that does not provide the minimum number of device objects for action mapping. Detected: 9 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. Joystick added to list Found joystick element: Z Axis Smoother created: Z Smoother z 8 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: 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: Collection 0 - Joystick GUID_Unknown detected Found joystick element: Collection 1 - Pointer GUID_Unknown detected Using joystick elements: 9 buttons, 3 axes, 0 povs Input device found: Saitek Pro Flight Switch Panel Instance: 8-6-8--1-4668800 ProductName: Saitek Pro Flight Switch Panel Product: -611000000876876 Type: Device that does not fall into another category. Detected: 20 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 (2- Logitech USB Headset) : Starting... DXMixer Speakers (2- Logitech USB Headset) : Start succeeded DXMixer SPDIF Out (Creative SB X-Fi) : Starting... DXMixer SPDIF Out (Creative SB X-Fi) : Start succeeded DXMixer Digital Output Device (SPDIF) (High Definition Audio Device) : Starting... DXMixer Digital Output Device (SPDIF) (High Definition Audio Device) : Start succeeded DXMixer Speakers (Creative SB X-Fi) : Starting... DXMixer Speakers (Creative SB X-Fi) : Start succeeded SoundManager: DirectSoundCaptureEnumerate DXCapturer Primary Sound Capture Driver : Starting... DXCapturer Primary Sound Capture Driver : Start succeeded DXCapturer Microphone (2- Logitech USB Headset) : Starting... DXCapturer Microphone (2- Logitech USB Headset) : Start succeeded DXCapturer Digital-In (Creative SB X-Fi) : Starting... DXCapturer Digital-In (Creative SB X-Fi) : Start succeeded DXCapturer Line-In (Creative SB X-Fi) : Starting... DXCapturer Line-In (Creative SB X-Fi) : Start succeeded DXCapturer Auxiliary (Creative SB X-Fi) : Starting... DXCapturer Auxiliary (Creative SB X-Fi) : Start succeeded DXCapturer Digital Input Device (SPDIF) (High Definition Audio Device) : Starting... DXCapturer Digital Input Device (SPDIF) (High Definition Audio Device) : Start succeeded DXCapturer "What U Hear" (Creative SB X-Fi) : Starting... DXCapturer "What U Hear" (Creative SB X-Fi) : Start succeeded DXCapturer Microphone (Creative SB X-Fi) : Starting... DXCapturer Microphone (Creative SB X-Fi) : 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.

Error log: 11/3/2009 19:31 V512091930 TrackIR DLL path: C:\Program Files\NaturalPoint\TrackIR4\ TrackIR DLL path: C:\Program Files\NaturalPoint\TrackIR4\ Errors Log: 11/3/2009 19:31 Command Line : ActionProcessor::Reinitialize System Log: 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: 8 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: 8 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: SideWinder Force Feedback 2 Joystick Instance: 11350--1-1668800 ProductName: SideWinder Force Feedback 2 Joystick Product: 9420000000876876 Type: Joystick. Subtype: Standard joystick that provides the minimum number of device objects for action mapping. Detected: 8 buttons, 4 axes, 1 povs DIDC_ATTACHED: The device is physically attached. DIDC_DEADBAND: The device supports deadband for at least one force-feedback condition. 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. DIDC_FORCEFEEDBACK: The device supports force feedback. DIDC_FFFADE: The force-feedback system supports the fade parameter for at least one effect. If the device does not support fade, the fade level and fade time members of the DIENVELOPE structure are ignored by the device. After a call to the IDirectInputDevice8::GetEffectInfo method, an individual effect sets the DIEFT_FFFADE flag if fade is supported for that effect. DIDC_FFATTACK: The force-feedback system supports the attack parameter for at least one effect. If the device does not support attack, the attack level and attack time members of the DIENVELOPE structure are ignored by the device. After a call to the IDirectInputDevice8::GetEffectInfo method, an individual effect sets the DIEFT_FFATTACK flag if attack is supported for that effect. DIDC_SATURATION: The force-feedback system supports the saturation of condition effects for at least one condition. If the device does not support saturation, the force generated by a condition is limited only by the maximum force that the device can generate. After a call to the IDirectInputDevice8::GetEffectInfo method, an individual condition sets the DIEFT_SATURATION flag if saturation is supported for that condition. DIDC_STARTDELAY: The force-feedback system supports the start delay parameter for at least one effect. If the device does not support start delays, the dwStartDelay member of the DIEFFECT structure is ignored. Joystick added to list Found joystick element: X Axis Smoother created: X Smoother x 0 Found joystick element: Y Axis Smoother created: Y Smoother y 4 Found joystick element: Z Rotation Smoother created: rZ Smoother rz 20 Found joystick element: Slider Smoother created: S Smoother slider 24 Found joystick element: Hat Switch 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: Effect Block Index GUID_Unknown detected Found joystick element: ET Constant Force GUID_Unknown detected Found joystick element: ET Ramp GUID_Unknown detected Found joystick element: ET Square GUID_Unknown detected Found joystick element: ET Sine GUID_Unknown detected Found joystick element: ET Triangle GUID_Unknown detected Found joystick element: ET SawTooth Up GUID_Unknown detected Found joystick element: ET SawTooth Down GUID_Unknown detected Found joystick element: ET Spring GUID_Unknown detected Found joystick element: ET Damper GUID_Unknown detected Found joystick element: ET Inertia GUID_Unknown detected Found joystick element: ET Friction GUID_Unknown detected Found joystick element: ET Custom Force Data GUID_Unknown detected Found joystick element: Sample Period GUID_Unknown detected Found joystick element: Trigger Repeat Interval GUID_Unknown detected Found joystick element: Duration GUID_Unknown detected Found joystick element: Gain GUID_Unknown detected Found joystick element: Trigger Button GUID_Unknown detected Found joystick element: Y Axis GUID_Unknown detected Found joystick element: X Axis GUID_Unknown detected Found joystick element: Direction Enable GUID_Unknown detected Found joystick element: Unknown 63 GUID_Unknown detected Found joystick element: Unknown 64 GUID_Unknown detected Found joystick element: Start Delay GUID_Unknown detected Found joystick element: Effect Block Index GUID_Unknown detected Found joystick element: Fade Level GUID_Unknown detected Found joystick element: Attack Level GUID_Unknown detected Found joystick element: Fade Time GUID_Unknown detected Found joystick element: Attack Time GUID_Unknown detected Found joystick element: Effect Block Index GUID_Unknown detected Found joystick element: Parameter Block Offset GUID_Unknown detected Found joystick element: Unknown 73 GUID_Unknown detected Found joystick element: Unknown 74 GUID_Unknown detected Found joystick element: CP Offset GUID_Unknown detected Found joystick element: Negative Coefficient GUID_Unknown detected Found joystick element: Positive Coefficient GUID_Unknown detected Found joystick element: Negative Saturation GUID_Unknown detected Found joystick element: Positive Saturation GUID_Unknown detected Found joystick element: Dead Band GUID_Unknown detected Found joystick element: Effect Block Index GUID_Unknown detected Found joystick element: Magnitude GUID_Unknown detected Found joystick element: Offset GUID_Unknown detected Found joystick element: Phase GUID_Unknown detected Found joystick element: Period GUID_Unknown detected Found joystick element: Effect Block Index GUID_Unknown detected Found joystick element: Magnitude GUID_Unknown detected Found joystick element: Effect Block Index GUID_Unknown detected Found joystick element: Ramp End GUID_Unknown detected Found joystick element: Ramp Start GUID_Unknown detected Found joystick element: Effect Block Index GUID_Unknown detected Found joystick element: Custom Force Data Offset GUID_Unknown detected Found joystick element: Custom Force Data GUID_Unknown detected Found joystick element: Y Axis GUID_Unknown detected Found joystick element: X Axis GUID_Unknown detected Found joystick element: Effect Block Index GUID_Unknown detected Found joystick element: Op Effect Start GUID_Unknown detected Found joystick element: Op Effect Start Solo GUID_Unknown detected Found joystick element: Op Effect Stop GUID_Unknown detected Found joystick element: Loop Count GUID_Unknown detected Found joystick element: Effect Block Index GUID_Unknown detected Found joystick element: DC Enable Actuators GUID_Unknown detected Found joystick element: DC Disable Actuators GUID_Unknown detected Found joystick element: DC Stop All Effects GUID_Unknown detected Found joystick element: DC Device Reset GUID_Unknown detected Found joystick element: DV Device Pause GUID_Unknown detected Found joystick element: DC Device Continue GUID_Unknown detected Found joystick element: Device Gain GUID_Unknown detected Found joystick element: Effect Block Index GUID_Unknown detected Found joystick element: Sample Count GUID_Unknown detected Found joystick element: Sample Period GUID_Unknown detected Found joystick element: Collection 0 - Joystick GUID_Unknown detected Found joystick element: Collection 1 - Pointer GUID_Unknown detected Found joystick element: Collection 2 - PID State Report GUID_Unknown detected Found joystick element: Collection 3 - Set Effect Report GUID_Unknown detected Found joystick element: Collection 4 - Effect Type GUID_Unknown detected Found joystick element: Collection 5 - Axes Enable GUID_Unknown detected Found joystick element: Collection 6 - Direction GUID_Unknown detected Found joystick element: Collection 7 - Set Envelope Report GUID_Unknown detected Found joystick element: Collection 8 - Set Condition Report GUID_Unknown detected Found joystick element: Collection 9 - Type Specific Block Offset GUID_Unknown detected Found joystick element: Collection 10 - Set Periodic Report GUID_Unknown detected Found joystick element: Collection 11 - Set Constant Force Report GUID_Unknown detected Found joystick element: Collection 12 - Set Ramp Force Report GUID_Unknown detected Found joystick element: Collection 13 - Custom Force Data Report GUID_Unknown detected Found joystick element: Collection 14 - Download Force Sample GUID_Unknown detected Found joystick element: Collection 15 - Effect Operation Report GUID_Unknown detected Found joystick element: Collection 16 - Effect Operation GUID_Unknown detected Found joystick element: Collection 17 - PID Block Free Report GUID_Unknown detected Found joystick element: Collection 18 - PID Device Control GUID_Unknown detected Found joystick element: Collection 19 - Device Gain Report GUID_Unknown detected Found joystick element: Collection 20 - Set Custom Force Report GUID_Unknown detected Found joystick element: Collection 21 - Create New Effect GUID_Unknown detected Found joystick element: Collection 22 - Effect Type GUID_Unknown detected Found joystick element: Collection 23 - PID Block Load Report GUID_Unknown detected Found joystick element: Collection 24 - Block Load Status GUID_Unknown detected Found joystick element: Collection 25 - PID Pool Report GUID_Unknown detected Using joystick elements: 8 buttons, 4 axes, 1 povs Input device found: Logitech USB Headset Instance: -5521--1-1668800 ProductName: Logitech USB Headset Product: 1411000000876876 Type: Device that does not fall into another category. Detected: 8 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.

Can I just get a refund for Flaming Cliffs, since there is no admin here with any apparent knowledge as to what this issue is?

Did that long ago. Admin BS is completely disabled. This issue is related to something else. Its not indicating a runtime error. It just hangs while on the loading screen and sits there. Control/Alt/Del indicates program not responding.

After messing with about everything, I think I found the best solution was to lessen the FF effects to around 30-40%. Its playable now, although I'd prefer a bit more resistance when I zero my trim. Still confused as to why everyone says the msffb stick is the best ffb device; I believe it is on many other sims, but here its a known issue that it doesn't respond to trim adjustments properly on high feedback settings. Hopefully they will fix it on the next patch.

I am taking a break from DCS BS to play some LOMAC. Sporadically, about 50% of the time, I get a freeze (app hang) during the LOMAC loading screen. Cant seem to find what the issue is. I am running the newest Flaming cliffs mod with updates, and everything on my system is current. Is this a known problem? Computer is stable, all drivers are current, and all voltages and clocks have been tweaked to perfection over the last 3 months. I suspect it is an nvidia driver issue, as that's where 90% of my past issues have seemed to come from. Would appreciate any advice. Vista 32 8800 Ultra dual 8500 @ 4.22 creative x-fi Also, is there somewhere where I can find optimum Nhancer settings for this program?