Rolds

I will add a link to a video once it uploads. In this case 5 Ju-88's were hit during a mission and the crews bailed out. After that the abandoned planes do not loose either speed or altitude and continued to circle indefinitely. Tacview file also attached. Tacview-20250628-110307-DCS.zip.acmi

Hi I want to fly with you guys, let me know if you're interested.

FM already feels great with a TM warthog+pedals, no extension. The pedals are very important.

I have a new theory I want to run by people, does the essex need to be the lead ship of any group (in other words, unit 1 of X in any group you place it in?) I just ran a quick experiment where I couldn't trap if essex was other than ship 1, but could when I re-ordered the ships so it was. I no longer think I have a map dependent issue, I have been able to trap on Marianas today.

Have you ever had the hook catch on Marianas or any other map? Does it work when you try on Caucuses?

I am pretty sure this is a software issue. I have not had a single instance where the hook engaged a wire on a map other than caucuses. I tried three times on Marianas WWII, then another two on Syria just for good measure. Then I go back to caucuses and I trap 3 for 3. This is the worst kind of bug, inconsistent, only applies to certain users, and I am one of them... I'm going to try running a repair.

This isn't a technique issue, the hook clips into the ship and doesn't interact with the wire sometimes. It appears to be map dependent and not universally affecting users. When you are just taxiing around on the Essex with the hook down I notice it clips into the deck and does not interact with the wires (caucuses and other maps). I bet this is having something to do with it. Wish I knew why it only seems to affect some users.

Contacting the Essex via radio is not required to trap. And I am still having issues with this which appear to be map based. I can now trap consistently on the caucuses training mission and a caucuses mission I created myself, but the hook does not seem to interact with the wires on Marianas, I haven't had a single trap there.

I have a problem like this. I was able to trap just fine in the training mission, which is on the Caucasus map. I built a mission in 1944 Marianas and was never able to trap on that in several tries. Same with a mission I tried on the Normandy map. Finally I built a mission on Caucasus myself and I was able to trap first try. Something funny is up, I find it hard to believe no one has been able to trap on the other two maps I mention?

If you are right (and your DCS knowledge has impressed me before, I remember you provided a script that helped prove the S3B refueling rates weren't working properly), this would explain the issue I have. Search then engage in zone sometimes does appear to work, but I often set very large zones so that the edge of the zone is straighter and starts to approximate a straight border. If your information on a 50% buffer is correct, that 50% area would be very large in many of the missions I create, giving the impression that search then engage in zone isn't working at all. Fully agree, being able to adjust the buffer zone would greatly improve things.

Could their detection and performance be modified? Or their tactics?

Then why do the other DSCG display options exist? I don't care for this answer at all, I am not interested in being constrained into how you think the F4 would be used. Having a verbal command for the WSO to change the aspect mode already exists in boresight mode (obviously), so why is it so difficult to believe this communication/coordination would never occur between pilot and WSO in other situations? And your reluctance to allow this type of interaction and proposed solution omits the heading information from the DSCG. Your response is surprising and seems illogical to me, I am only asking for the ability to ask the WSO to flip a knob that I can already do when the radar is in boresight mode, that is all.

So all I am looking for here is a way to change the display on the radar so that in the pilot seat I can see information other than closure velocity. The reasons don't really matter but potential use cases include figuring out if the locked target is above or below my nose or correlating my lock with a radar controller in an intercept to confirm I have the right target in a complex environment. If I switch to the WSO seat I can move the knob and get this information to display, but if I ask Jester to do that he replies "unable". This appears to be an unnecessary limitation if not an outright bug. Is there any other way currently to change the displayed information on the radar screen from the front seat? If not, could you please allow jester to move the target aspect knob in situations other than boresight mode?

If I understand the manual correctly, especially this part about the boresight aspect knob that the WSO has, it has two functions, first to being to set the speed gates for boresight radar, and second to select which information is to be displayed on the display readout at the top of the radar display when a target is locked. Jester does not seem to be able to change this knob to other positions except when boresight mode is selected, but there doesn't appear to be anything stopping him from doing so, and I would like it if he could so I can select what information will be displayed about the locked target. I'm not posting this in bugs yet as I am still going through the F4E, can anyone tell me if I am missing something here? EDIT - after I typed this out I realized I could just hop back into the WSO seat and try this, and sure enough you can switch this knob at any time. I think this is a bug, Jester should be able to change the boresight aspect knob using the interface and direct commands (there are buttons that do this that are helpful to bind) at any time.

This problem still exists on October 26, 2024, and the advanced waypoint options idea does not stop Mig 21 (or other AI aircraft) from using flares even when they have none aboard. When people talk about fixing core game mechanics, this is exactly what they mean. @BIGNEWY How can such a basic problem last for years without being fixed?

A flock of hot air balloons lurks somewhere on the map, does that count?

As we come up on two years with no action on this simple deficiency I am left to believe that no one who works for eagle dynamics has become proficient enough at this game that issues of night refueling matter to them.

When this "Start Enroute Task" item is set for AI aircraft, the behavior I would like to see is that these aircraft will only engage other aircraft within the set zone to depict situations where fighters will not chase an enemy across the map into hostile territory. However, this is not the way this feature appears to work. The AI aircraft to appear to only engage aircraft within the zone, but once this happens they never disengage. I would like a feature that makes AI aircraft only engage enemy aircraft within a set zone (and if I could set the shape of said zone that would be even better).

I have the same problem, rockeyes appear to function a very short time after weapon release regardless of fuze option selected, makes anything other than low altitude attack inaccurate to the point of not being usable.

Rotating the windshield wiper knob on the roof panel doesn't seem to do anything and I cannot find any other controls for them, is there any way to activate them? Rainy weather landings are hard!

Could we get an option that would allow us to prevent aircraft from strafing ground targets? I have many situations in mission editing where I only want aircraft to attack ground targets with their weapons other than the gun, and removing the gun ammo doesn't always work, mostly because there are times when I want that retained for air to air combat.

I haven't been able to get it to fire, is this still not implemented? Will it ever be?

Does the F16 have access to these? I can't find them on the payload tab in the ME.

I would like this to work just like "Part of group in zone" but be able to set a moving zone around a unit. The use case I am looking for is to have a unit moving but stop when it gets close to enemy units and notify me that its way ahead is blocked (with JTAC designation via the CTLD JTAC script), and having a part of coalition inside moving trigger zone would be an efficient way to achieve this. There would be many other potential use cases like being able to flip a units ROE or alarm state easily.