RedeyeStorm

I am not sure if this is operator error, DCS issue or something you guys can address. I have been flying he F4E in the Iran-Irak campaign. Flying mostly Sead missions as the campaign is just started. When we reach the IP point I order my wingmen to ‘Attack primary and rejoin’. What happens immediately is that my wingmen start flying towards waypoint 1. Now I have noticed before that the waypoints on the F10 map never increment. The yellow dashed line always points to waypoint one. With previously run campaigns flying a Strike mission this was not an issue but I am wondering know. The Sead mission does not have concrete target to attack unlike a strike mission. Wondering if that causes my wingmen to return to waypoint 1. Any ideas?

And where do I find/input this?

@Miguel21, I have indeed set optview_all but when I check the mission all enemy air have the 'hidden' option activated. Iran-Iraq war-IRIAF_ongoing.miz

Hi all, I suck at these missions and I keep getting owned because I do not know what exactly is happening. I would like enemy planes to be visible on the map. Can you tell me how to go about this please? I have mapoptions set to All but it only shows the ground forces and ally planes. Thanks.

Yes I understand. It does not happen every flight.

Hello folks, Possible issue. I was trying to do some Aerial refueling and Jester was giving instructions but suddenly all I got was a static sound. Jester never started talking again. Tried silinceing him and start talking again through the wheel but no joy. Wheel commands worked just fine just a terrible static radio noise the rest of the mission. ATC and AWACS worked fine. Known issue? If not I’ll try to provide a track (I did a search but found no posts)

+1

Please read the post of @A Hamburgler and not only your own words.

@draconus, Saïd that using medium textures means that lower resolution skins are used. How much lower no idea because I haven’t tried it. My DCS runs at 10 fps so grounded until fixed.

That does happen but in this case the reports (including my own experience) all indicate that without any hardware or setting changes the fps dropped after the update(s). In my case from 45 fps in flight to 10 fps in flight. That is not outdated hardware that is a software problem. Hardware would only become outdated after a major feature update. This is not the case with the recent updates.

Would be nice if we could opt out 4k skins.

Fingers crossed it comes soon because DCS is grounded at the moment.

Considering all the posts regarding performance of DCS in general I now doubt there is any relation to the F4.

@Leva80, I agree to a point no way to know if it is ‘most’ but then again you do not know either it is not. Why would I repeat something that is already said by someone else?

I am flying VR so no VSync.

Problem has been with us for a long time. There is a work around by editing the start waypoint through advanced waypoint editing. You can disable contact reporting by your flight. Also works through the ‘missionplanner’ before pressing fly.

Hi @Silhou, thanks. I already have applied that solution, have been using that for some months now and have been using MT since it came out. I have run some tests with the next to last update and have found that affinity and priority settings do not make much if any difference (couldn’t notice a difference in play) on my system (I9-9900K, 32mb RAM, nvidia RTX 3080). Also tested ST but performance was definitely worse. PS you guys delivered once more a beautiful module.

Can we have some pics from the cockpit please?

What weapon where they equipped with? I found dumb bombs work fine but agm 65 do not, nor Walleyes. My wingmen usually crash into the terrain at some point.

@Elf1606688794, you are being nasty. @Zabuzard suggestion for trying to lock it your self is not intended as a workaround but a remark that would show you how 'bad' Jester is at his job or he can't because the radar in the Phantom is not verry good in that situation. He then states that if Jester can't lock on and you can that you provide a track so Jester can be improved. You are just venting without effect.

Hello, I have been experiencing a sever drop in perfomrance between version 2.9.6.57650 and 2.9.6.58056. In the older version I was enjoying for me exactable performce (34 to 42 fps in busy missions.). With the latest build this is severly reduced to 7 and 15 fps in the same mission. I have been running the same mission in both versions. Have attached my settings in DCS and SteamVR, DxDiag and the DCS.log files form both versions. Also the mission is attached. I consider it likely that the ground forces are the culprit here. In version 2.9.6.58056 I enjoy good fps until I get near ground forces. Unfortunatly I was unable to save the tracks. Got an error message. DxDiag.txt Iran-Iraq war-IRIAF_ongoing.miz dcs version 29657650.log dcs version 29658056.log

I have the same issue with the Phantom and posted this a well. No issues with other planes and the Tomcat was always a bit heavy on the frames. My limited testing with the Cat saw no difference.

The most simple answer would be that none are made. You can check in the mods control lua if there are any custom inputs there. Sorry that I am vage about where and what file you need but I am away from pc.

I have been experimenting with the improved spotting on/off but I can’t tell the difference. Granted may be my bad eyesight but if given a choice I would choose the previous version of 2.9.5. Do agree with the criticism on that but now I am blind and have to cheat with F5 to have any fun at all. This is my personal opinion and not going to change.

And wrong again. It’s a game people should have fun! If I am not mistaken you @draconus play mostly MP am I right?