

Rolds
Members-
Posts
583 -
Joined
-
Last visited
-
Without getting too into the weeds on this issue just step back and think about the big picture. Could the R2800 possibly have achieved the reputation for reliability it had if it worked like it currently does in the Corsair? I suggest people fly the P47 module that ED did and compare the two. I particularly like that the ED radials offer audible feedback about operating out of limits, and have partial failures or will fail overtime rather than always instant and total failure. You can fail the P47s engine, but it puts up with a lot before it quits, matching its reputation.
-
FUSE SELECTION DOES NOT WORK.trkSee Attached Track. In this situation the bombs are equiped with 11 second delay tail fuses and instantaneous nose fuses. With Tail fusing selected, the nose fuse should not function, resulting in 11 second delay. With Nose/Tail selected, both fuses should function, resulting in instantaneous explosion. As you will se in the track, with tail fusing selected, the bombs explode immediately on contact with the ground. The nose fuse should not function in this situation (except in cases of weapon malfunction which is not modeled in DCS and in any case the results are consistent in all of my tests).
-
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
-
- 1
-
-
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?
-
[Bug] Jester calls out "lost cabin pressure"
Rolds replied to streakeagle's topic in Bugs & Problems
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. -
[Bug] Jester calls out "lost cabin pressure"
Rolds replied to streakeagle's topic in Bugs & Problems
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. -
[Bug] Jester calls out "lost cabin pressure"
Rolds replied to streakeagle's topic in Bugs & Problems
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 -
[Bug] Jester calls out "lost cabin pressure"
Rolds replied to streakeagle's topic in Bugs & Problems
I get this erroneous call all the time when flying on Nevada. Whatever logic is going into it, strongly suggest you reconsider. -
Deck Crew AI directing me on to blocked cat.
Rolds replied to DmitriKozlowsky's topic in Bugs and Problems
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. -
reported JU 88's continue to fly indefinitely after crew bails out
Rolds replied to Rolds's topic in Bugs and Problems
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. -
Deck Crew AI directing me on to blocked cat.
Rolds replied to DmitriKozlowsky's topic in Bugs and Problems
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? -
reported Ground Unit LUV Tigr: no more lights at night?
Rolds replied to cfrag's topic in Object Bugs
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!
- 1 reply
-
- 5
-