last1976

So now I ve done some more flights I can now more exactly tell what is happening. 1. It is only happening in early years without Gps available 2. It is not the Auto Mode wich is failing. If I designate a target over any sensor besides the HUD CCRP is working fine. By the way CCIP is working fine too. 3. The only thing which is not working is to designate a target via HUD. 4. If I designate with radar or tgp, I can do an auto bomb run, how I want, I can Dtos, Level Bomb it is all working, but I see the targetbox in the Hud is way off the actual target, but still If i fly the Line, I hit the target, wich kind of makes sense that if I put the target box over the target manually in the Hud, it is the other way around and the bombs are way of. TRACK_CCRP_FAILING_HUDDESG.trk

So I ve flown around a little. Please note the track, I will provide tomorrow, as my time is really limited today. But for an update. If I set mission Date to 2006, the bombs fall, lets say believable. In a second run I choose gps in the HSI Pos Menu, and the bombs hit on point. Back to 1989 Mission Date, they are not even near.

It’s 1989. It’s a self set up Trainingsmission I start 25 miles out of the target.

I will but this can last two days. Is it possible I have to align INS properly? I am starting in the air . And I’ve noticed the Ins is on Nav as default configuration

When I designate the target via HUD im Auto Mode. The Bombs come in nowhere near the target. The Calculated Solution seems way of the actual designation point

So i ve purchased a samsung 980 pro ssd. All is running smooth now. Same experience as stonewall197922. But I want to point out, the new Radar Features had definetely decreased the ability of my system to perform as before. With the new ssd I although managed to crank up my graphics a little bit, running at stable 75 -100 Fps. Right now I am fiddling with the preload radius setting, Suggestions would be welcome.

I have no script folder either. I think after renaming the saved Games folder. Cleanup and repair it is supposed to be like that. No Mods installed yet

After exercising all suggestions, the Problem is still there. As long as the AA Radar is working. When I press Silent or turn it of. All is running smooth. Question to the devs. Is the AA Radar supposed to be such an massive impact on the system or are you considering it has to be something off if it has an noticable impact, especially in form of stuttering an freezes? Because as the other posters, i can definetly confirm it is the AA Radar causing the Issue.

Hallo Flappie, if gone now through all of your suggestions. But the Problem stays. I managed to kind of get my sim flyable, for example if I turn down preload radius to 100, the spikes, freezes are not this massive anymore. But I want to point out they are still there. And they are clearly bound to the AA Radar. If i turn it of or press silent I have smooth fps graphs, in the moment I turn it on i gets weird. i dont know how much the AA Radar is supposed to consume fps or be a mentionable load on Hardware, but it seems to me something is of since the last patch. I hope you guys will take a look at it, because right now it seems to be a mess.

Same Problem here. Something seems very off. I cannot even fly after takeoff, freezing for 10 plus seconds. When I turn of radar all is butter smooth

I have done the cleanup and repair so far, not deleted saved games folder. Same Problem no difference, but as I allready had fired up the game, I selected again my f-18 on carrier, did the same startup without turning on radar. And that was it, super smooth like it has always been. First Question: Does it still make sense to do the steps with deleting the game folder and if not. Second Question: Is there a solution available to this allready?

the pagefile setting you can see on the attache picture, the used harddrive for it is an ssd. You suggest setting the pagefile on manual up to 32000mb? The other suggestion of you I will try.

There you Go dcs.log

Since the last update (OpenBETa 2.8.6.41066.1,) i cannot play any longer. First I want to state, that until now the game ran smooth without problems since months. Now I fire up my f18 on the carrier rolling to the catapult, and as soon i am of the deck the game freezes. No Crash just freeze to 5 frames per minute. Anyone have an Idea?

Exactly my Problem, maybe should have pointed out too, that before last Beta update I had it running smooth. What I have researched so far. No issues with ram usage, cpu usage and harddrive while happening. But Graphics Card drops significantly to very low usage level for the time of the lag/stuttering.

Same!! On Multiplayer even worse

I have the same findings. Manual Pip bombing works on bomb mode not on gun mode. In gun mode it is just impossible to get the piper constantly on target.

In my Opinion something is wrong, with the bombing training mission. It says to switch the sight selector to gun for manual pip bombing. But it seems not to work at all in this position. If the selector switch stays on bomb it seems to work normal. Even in the docs the error seem to be present.

So I wonder If this bug is considered as worth to work on it, because now we are nearing his monthly birthday ? Im getting concerned.

Even if this is true, which I highly doubt because there are many users who are using steering wheel pedals. Some because of financial reasons, some for practical reasons (like me) etc. For me right now it isnt the problem that the bug exists. For me the Problem is that it has made its way through to release version. This is the really annoying part for me. If a patch / version etc. isnt ready for release, just dont release. And maybe it would be better to reconcentrate on quality and developing models everyone is now waiting for years instead of pulling out a new model every month. Until now I ve purchased every module, that came out. But if this policy continue I never will again, because free times are to rare to waste them with stuff that is not working.

For me it worked in the first place. After some longer flights I have to say, this "workaround" isnt stable for me. It seems that after some undefined time, trimming stops working. I really hope we dont have to wait long for the fix, and for the future I suggest ED to stop pulling out patches on release which havent gone through a basic qualitiy control and Beta testing. Why we are running DCS on 3 versions, if their arent used for that purpose ?

100% agreeing. But try to start unconnected with pedals and wait until youre sitting in cockpit, then reconnect Pedals, since last patch this works for me. Still pretty annoying but a possible workaround, but you have to do it everytime youre changing cockpit or go back to main menu. to be clear, i every case you have to restart DCS unplugged from device. It is not working from Main Menu to Ingame.

another problem that I never had, until now if I am looking somewhere else, all I had to do was to recenter trackir when coming back to screen. Now trackir seems to disconnect, if I wait too long it freezes until I restart DCS. You guys really no how to ruin stable version.

All I can say to this is W T F s wrong. Sry but right now............. this is just nothing but ridiculous.

Well I will try this tomorrow if I find some time, just for investicative reasons. But correct me if I am wrong. Basically you ask me to trade my Rudder Pedals for the ability to trim the aircraft ? I am not amused.