whataboutbob71

Like I said he isnt targeting what he should be targeting. I'm telling him to target ahead where the sight is pointing and he is still off the screen trying to lock something else. He does this repeatedly! There were live armored targets still there because they shot at me multiple times.

Fortunately my backups work, but the size is over 50MB. Lift the limit and Ill attach it; its 85mb. It shows peter either not locking anything, continuing to lock something out of sight, or locking low priority targets. Here is a video segment of the issues https://www.twitch.tv/videos/2127243415

My experiences are on multiplayer servers. I must assume you "testers" don't test in those environments. Many times pete has not targeted anything even when the hostile units are firing at us from the front and with me directing him to scan that exact area where the firing is coming from. Do I have a track, no, because we have to delete those along with the files in the fxo and metashaders folder just to reduce the risk of performance issues. I will say it always isn't occurring, pete being blind, but its well known problem. The fact we have to become testers isn't the correct response from a company charging money for new content when the current is still buggy as hell. I didnt even touch on petes inability to target closer threats over other threats further away leading to us flying into the closer threats firing range and dying, as RealDCSpilot mentioned above. Again my experiences are from online play. I would like to suggest you testers research regression testing methodologies and start implementing them. Else you may notice people no longer paying for new modules. And my investments in your software going down the drain.

Petrovich not targeting anything! Enough said, been like this the past two patches.

Just an update on this. It turned out to be XMP got enabled on my system and threw the memory frequencies out of normal. Took multiple memtest86 sessions to find this out. I set the memory back to use Auto and haven't had the issue since. Its strange though DCS was the only simulation game that trigger the events.

Its not hardware and by my original post I have gone through all possible hardware testing. DCS is the only game this happens with and only with the latest version. I've been playing DCS with the this RIG for over a year now. Is there a way to go back to 2.8?

the play time lasted longer but Im still getting BSOD. dcs.zip

Here it is dcs.zip

I am constantly getting Blue Screen Of Death crashes with the latest version. I have ran full memory diagnostics, check every disk, multiple version of video drivers, sfc ( system file checks ), OS Reformat and Reset, and a Full clean install of DCS. The stop error is either a Critical Process Stop message or a 0xc000021a stop code, nothing get written to the event log besides the improper shutdown message on restart. I have ran 3DMark 4k Extreme bench tests and a 4k Extreme Stress Test without issue. Other stressful games also rung without errors. 2.9 in general has been a major hit on my system and this latest patch has simply killed my ability to play the game for more than an hour because of the crashes. I watched a YT video one some changes you have made to "optimize" video performance so I thought I'd post this on the forum. Is there a way to revert back to 2.8? Hardware is a custom built PC. ASUS TYF Gaming Z790 Plus Wifi Motherboard BIOS 1641 Intel i9-13900K CPU 128GB G.SKill Memory Nvidia 3090 FE Video w/551.76 GR Drivers 2TB WD Black M.2 nVME Disk for OS and DCS There are other nVME and SSD drives on the system.

Would love to have the ability to provide forward arming and refueling point mission for strike aircraft. Long range SAR. ACH-47 gunship ability, "Spooky". Downed aircraft recovery, sling load other air frames back to base. Airborne!!! Drop troops or equipment out the back via parachute, or low and slow over water like zodiac inflatable boats.

On GrayFlag PG server and clearing out a town. The tank is shot by infantry with AK-whatever and it destroys the engine.

AAA units are shooting over mountain ridges at helicopters. Im behind a ridge flying away and they can still see me and better yet, yeet the round like mortars.

Just got done updating to the version released today and now all my modules are generating a 502 error. Thank you, Bob

RIP

found the post about deleting the bindings for the AV8 and it worked.

I'm unable to use the Sensor FWD, it's grayed out. I've tried using different bindings on my hotas and using the default keyboard command but it never works. Anyone else have this issue or is it a current bug in the build?

I found the issue, it was my rudder pedals. The toe presses were being mapped to aircraft control in the Axis Assign screen. When I was inputting rudder commands and pressing the toe in some, the aircraft went into some unexpected maneuvers. This causing me to try to correct my flight and then everything rolling into a big FUBAR. I cleared the Axis Assign for my peddle and mapped the Rudder and Toe brakes for what they are supposed to do. I haven't had the problem since, I have to do this for each of my modules. Strange the game would map toe presses to regular flight controls. I am using a Logitech/Saitek Pro Flight Rudders and an x52 Pro HOTAS.

It must have been the recent update that made it more realistic than. I was doing way worse a couple days ago and never had this kind of trouble. I mean I've ripped them off but I was also doing some extreme maneuvers for an extended amount of time.

I have been having random aircraft breakups. I start doing a couple barrel rolls in the harrier and then my wings go bye bye. So I flew a easy G sortie and in the end my plane begins to break up and I have to eject. I have just added a Logitech Rudder pedals and updated to the latest DCS client. Those are the only two changes to my setup and I have been having aircraft crack ups the past few hours. I have attached the latest crackup track to this issue. Any advice on how to identify and resolve the issue would be greatly appreciated. :pilotfly:

OMG, I just found the problem after posting this. It was the parking brake that was blocking the throttle. Had to lean forward with my trackIR and look in front of it.

I'm trying to do a cold start within a Fast Mission but I cant seem to disable the throttle cutoff lever. When I hit the key binds it just pops up, it wont move forward. When I try to use the mouse to drag it forward it just clicks back down. I just started playing a few days ago so I'm at a loss. I'm using an X52 Pro and any suggestions would be greatly appreciated.