egaRim

FFB seems good on G940. I could not feel a difference in resistance between pitch and roll.

Enabling AP now works with with my G940. Thanks a lot Heatblur and kudos for support ancient technology from the 90s! However, there seems to be an issue: If I enable AP (Attitude hold) and I want to override the AP to set a new attitude the manual says to just push over the force, set the new attitude and relase the stick. This seems to be borked in DCS. Example: I'm in a 1000 fpm climb and enable AP (attitude hold). I let go of the stick and the AP keeps my climb. So far so good. I now want to change from my climb to a 2000 fpm decent. When I push forward on the stick it seems as if I'm fighting the AP. The airplane tries to maintain the climb. This goes as far as I'm hitting the limit of my controller (full defelection forward) and I'm still in a climb. When I then let go of the stick the aircraft pitches up massively as if the was full aft trim. The cockpit indicator does not show any changes on pit ch trim though. My current workaround is to disable AP, set the new attiutde manually and then reenable AP. The downside of this is, that any other AP modes (alt hold, ground track) are disabled with the main AP switch.

Logitech G940 MFG Crosswind Pedals Saitek Trottle Quadrat Bodnar Board for custom Panels Thrustmaster MFD (2) Please keep FFB alive. Concerning defaults: Please allow an easy option to remove all default bindings except for keyboard with one click. The current defaults are in conflict when you use multiple controllers, e.g. 5 controllers mean 5 roll axis assigned.

I would love to see FFB support for the Hornet. Following effects would help a lot to feel the jet: increase in resistance as you pull more Gs same when your AoA goes above 22 as described in official document https://forums.eagle.ru/showpost.php?p=3281531&postcount=5 general shake effects as described above What's the current state of FFB implementation anyway? It seems to me that we only have a rather subtle center spring effect.

This is still an issue for me. I understand that the elevation control in the real thing works differently, but can we please have the option to use our existing controller axis (i.e. the further you move the axis, the further radar elevation changes, like it is implemented in all other jets with radar in DCS). I guess most of us don't plan to mod our hardware to exchange the axis control with an encoder or something spring loaded.

This issue still persists in current version.

I have the same issue. Only that TIR center resets the view to approx. 20 degree right and down. This also happens when TIR is paused. Where can I check DCS in cockpit default center view? Some lua files I guess?

Will invisibility of contacts on Nvidia cards (as compared to AMD) be addressed?

I had the pleasure to help testing the mission. Something completely different from previously known missions. Amazing what you can do with creative scripting. MBot is a wizard ;)

Very well put. I won't even consider buying any WVR-Dogfight related module until this major drawback of the DCS engine is fixed. This should be reviewed by the developers. Please give us a short feedback that you heard our pleas.

imo you need to reduce the interval when your script checks the probability. The way I see it, your sample chart is only valid for exactly one specific situation. It cannot be applied continously for your mentioned reason. One way out would be to trigger on certain thresholds (for example, every time the target closes a full 1000 yards probability of detection is calculated). Another possibility would be to restrict the interval by simulating the oberserver turning his head at a certain turn rate (say 5 degrees per second). This would result in an "All-Seeing-Eye radar like check" every 360/5=72 seconds, or, if you can pull it off, a direction specific check in a 5° search cone every second.

A short update: I repeated the mission that crashed but turned off the cloud overcast. Instead there were just scattered clouds. I could fly the whole mission without any crashes. Strange...

No Mods. I completely deleted the old folder of FC2.0 before reinstalling. How could I test for hardware defect? Would I look for RAM oder Video Memory? chkdsk didn't find defect sectors on my harddrive. No overclocking on my system either. It's plain stock.

I confirm, Catalyst AI was disabled.

Thanks for your reply. I will check Catalyst AI but I think it was disabled. Faulty Hardware would show up in other Applications/Sims, wouldn't it? I don't have any other stability issues outside FC2.0 I already cleaned my ATI-Drivers with a tool and cleanly installed the latest drivers. I also reinstalled the game. No joy. @Teknetinium Only one hard drive with serveral partitions. TIR-Driver and game on the same partition. I've Win XP. I don't seem to have a memory leak issue. Process Manager shows a constant memory consumption around 900 MB. I've read Mustangs posts in the long error-thread.

no feedback at all? I took my time to make a proper error report as is suggested in your FAQ, no answer seems a little disappointing......

Hello there, I have trouble with regular game crashes in FC2 v1.2.1. They seem to have occured after Patch 1.2.1. DxDiag is attached. My system runs other Sims (Rise of Flight, Sturmovik, Black Shark) just fine. Unfortunately the game doesn't always crash completely so that there is not much information. Recently I managed to get following crashlog: # -------------- 20100616-193451 -------------- D:\Games\LockOn Flaming Cliffs 2\bin\x86\stable\DXRenderer.dll # C0000005 ACCESS_VIOLATION at 0391081A 01:0001F81A # # EAX = 00000000 # EBX = 00000064 # ECX = 00000000 # EDX = 0BC60000 # ESI = 0C817898 # EDI = 00000064 # CS:EIP = 001B:0391081A # SS:ESP = 0023:0012F6F4 EBP = 3D44E4C8 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00210246 0391081A 3D44E4C8 0001:0001F81A D:\Games\LockOn Flaming Cliffs 2\bin\x86\stable\DXRenderer.dll ?Update@DXClipTexture@Graphics@@AAEXXZ()+3A 0391081A 3D44E4C8 0001:0001F81A D:\Games\LockOn Flaming Cliffs 2\bin\x86\stable\DXRenderer.dll ?Update@DXClipTexture@Graphics@@AAEXXZ()+3A BD0D39C0 3F7E8E90 0000:00000000 Error.log is attached too. Description of that "test case": 1. Hosted attached MP mission for around 10 minutes. 2. Restart of the mission and takeoff. After around 5 minutes into the mission I got transparent cockpit (see attached screenshot) but could continue flying. After flying through clouds in external view I got back my cockpit graphics. 3. I dumped flares (some every 10 seconds) in external view. 4. After around 5 minutes my game crashed right when I released another flare in external F3 view. I also get a regular "hang up". Same Mission about 20 minutes between waypoint 2 and 3. The view seems to snap towards the sky (blue or clouds). No Cockpit nor any other objects can be seen. I can't move the view with TIR or mouse. Sound of the mission continues. I can hear my engines when moving throttle, flare sounds even fly by sounds when I hit F3. But the view always keeps locked to the sky. I have to end the process in windows to get my system back under my control. Thus no crash logs in that second situation. Hope you can help / fix if it's a bug. Error.zip DxDiag.txt MP CWW-06-1.zip

Thanks. I suppose the range table is in km?

During the Red Bull Air Race 2006 in Berlin, pilots peaked at 14g or 15g (might be even more by now because they keep on pushing the limits) There are some tight low-level bends and they mustn't black out ;)

I personally have no problems with cyrillic HUDs or Cockpits (although I'd surrender to a cyrillic ABRIS). But English is quite common as foreign language (in contrast to russian). My point is, that translating the whole sim into several "minor" languages (including my mother tongue German) just delays the release of the sim although it is finished. So maybe a two staged release would be feasible. First finish russian (for it is ED‘s domestic market) and english version for world wide release. Then translate into other languages for non-english speakers. This would also generate some early revenues for the developers...

I wouldn't mind an english-only release first... English is kind of pilot language, isn't it? No immidiate need for localization...

confirmed - you can do that in IL-2 "on the fly" :smilewink: In general: The usability of LockOn's GUI is one of its major weaknesses... Hopefully this will be changed in upcoming DCS-titles.

Dogfight! Dogfight! Dogfight! :D Man, I guess you would measure turn rate in minutes...

What about ground details? Did they improve them? That was always one of the main flaws of the old third wire games to me.

sounds good. I will give it a try.