Rolds

Search Lights Off too Soon.trk See the attached track file. When an aircraft being spotted by searchlights is "killed" as the game defines that term, the searchlights immediately switch off. However, the "killed" unit is still flying, typically just with an engine on fire. Real searchlight crews would probably continue to track the aircraft if only out of fascination at the spectacle, not immediately switch off.

The attached track features two bugs. First is the bug I'm reporting: The Mig 21's in this mission are set to option "Chaff-Flare Using=Never Use". Despite this, they use flares in the mission. Second not reporting this one here as it has been reported several times elsewhere over the years, the Mig 21's in this mission are not equipped with chaff or flares as they are not carrying the correct pods and the airframe does not come with countermeasures by default. Despite this, they use flares anyway. This bug has already been reported elsewhere several times such as: As a bonus issue, the AIM 9x "counter-counter measure" performance seems pretty lackluster. Mig21's Use Flares.trk

SO how is that Jester customization coming along? It appears we still have no way of asking him for information about the target, and cannot switch boresight modes to get that information repeated to the pilot?

lol never mind! Jester is making the call in all sorts of nonsense situations and I have no idea what logic is behind it. Would be better if he didn't make this call at all. EDIT - and while we are on the subject, if you are going to have this call could Jester please sound less panicky about it? We both have O2 masks on. The unpressurized altitude record is apparently over 70,000 feet. We aren't in any danger even if Jester was right about the cabin pressure.

If you disable the call for cabin altitude <11,500 feet that would fix the situation where the call is made if you dive below the cabin altitude and it takes longer for cabin altitude to catch up than the current jester logic.

This track breaks as when I watched it the mig's position isn't what it was when I flew it, but it includes the "WE'VE LOST CABIN PRESSURE" call which is occurring for me on every flight. WEVE LOST CABIN PRESSURE!.trk

I get this erroneous call all the time when flying on Nevada. Whatever logic is going into it, strongly suggest you reconsider.

Does it not work with the supercarriers or maybe I just don’t know how to do it anymore? I was using CVN 72, taxied into position, lowered the launcher, pressed the bind which I think was U, but nothing happened.

This was also reported in this locked thread. This problem was also in the game years ago and they fixed it, but have somehow unfixed it and left it unfixed for two months and counting now.

Could we maybe get the ability to manually connect to a catapult back to work around this vexing problem???!!! OR request which cat we will be directed to?

Any progress on this? I was planning to use the LUV tigr as a signal light for a mission only to discover its functionality changed and found this thread. By the way giving us more options for lights at night (spawn able and de-spawn able, ability to signal with morse, changing color) would be really helpful! Also, shouldn't all vehicle lights work like the LUV tigr? why is it special? Shouldn't we have an option to select if vehicle lights are on or off at night?

Here you see a couple images of an aircraft with its external lights on and a signal flare activated through triggered actions for comparison. In general, aircraft lights are only visible from a few hundred feet away. The signal flare on the other hand is visible from miles away. Everyone has seen aircraft with their running lights on at night, visibility in miles is accurate as that is the point of the lights. It would really help with night flying if aircraft lights in DCS had realistic draw distances. I feel like there must be a simple fix, just make them work like the signal flare!

I really think someone should look into this, for one thing I am pretty sure the fuses are independent of one another, therefore the implementation is wrong. And for another, someone who just buys the spitfire and tries it out is immediately going to wonder why the bombs don't work.

Reference this thread. @Flappie appears to think this issue is resolved but it is a bug that persists. Spitfire 250lbs bombs do not explode on contact with the nose fuse set to contact and the tail fuse set to the default 30 minute delay. These fuses operate independently and both are armed when the plane takes off, therefore the nose fuse will cause the bomb to detonate immediately, however it does not. Spitfire Bomb Fuses Not Working.trkSee the attached track. The bombs have the default instantaneous fuse in the nose and 30 minute fuse in the tail. The bombs hit the ground just after 5:25 in mission time and explode 30 minutes later.

In fact it doesn't appear to work at all. See the attached mission which tests a few embarking/disembarking things. LCVP 1 is supposed to start the mission with Commando 1 aboard, similar to the way Commando 2 starts aboard the UH1 Huey. As you can see it doesn't work, they spawn on the beach rather than in the LCVP, despite apparently being set up the same way as Commando 2. Commando 3 and LCVP 2 shows the LCVP embarking feature working surprisingly well when picking up a group from a shoreline. The LCVP ramp is animated, the commandos get on board and are visible on board, the LCVP backs away from the shore and sails away. All good stuff, I just want a way to have infantry aboard the LCVP's at mission start for amphibious assault scenarios. I can't right now think of a way to accomplish this. Operation Forager.miz