defeatist99
-
Posts
172 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by defeatist99
-
-
On 8/22/2021 at 6:19 PM, captain_dalan said:
Just did the same test as before in the F-16 and the F-18. In both planes the RWR starts the launch warning as soon as the bandit fires the missile. It also doesn't stop until the missile hits you or misses you completely.
On the other hand, in the F-14A and B, the RWR starts the launch warning as soon as the bandit fires, but around 45 nautical miles it switches back to being locked warning. So this is an F-14 SPECIFIC issue, and quite possibly a BUG!
Can anyone else confirm this? Someone from HB or a mod?Thanks for testing and confirming it's not just me! I just bumped the thread because I don't know where to put it here or over to ED.
-
3 hours ago, captain_dalan said:
1. That is indeed weird. Never happened to me before but if it's constantly repeating to you, then it's definitely worth investigating.
2. This is why i suspected home on jam. Have you talked to someone from ED about this? Is it a missile feature? This does happen to me as well if i don't take any action after launch. The RWR will go haywire on launch, then go silent, then the missile will hit. However i have zero knowledge on the operational behavior of the MiG-31/R33 weapons system as a whole, or how that translates to DCS. All i know is that it should FOX-1 guided by a PESA, but it wouldn't be the first time DCS engine limitations resulted in wonky feature implementations. I.E. the AI counter-measure-ing the instant you launch at them, despite you launching passive or TWS guided ordnance
Yeah, I mean I'm not sure where this issue should go then. I'm trying to get the issue reported and that's why I'm here. And yeah, you are correct. It is a fox 1 but it has an INS. So it should be able to launch without giving an immediate warning but it should be screaming at you for all of terminal guidance because it still needs to be guided by the 31 radar. If it's giving launch tone immediately then it stops it's backwards from what it should be.
-
10 hours ago, captain_dalan said:
Just did some tests against the MiG-31. My intent was to test launches from different altitudes in an attempt to correlate launch warning with RWR blind spots. Alas, the AI would not cooperate as desired. Still, all launches were detected.
My hypothesis:
Either the MiG locked you from a blind spot, or he has lost the lock, but the missile HOJ-ammed you. Were your ECM on during the encounter?ECM shouldn't have been on. It's possible I guess but I would have to double check with my rio. It happened to me again yesterday on stream. It seems to me that it has to do with previously receiving a launch tone and not receiving subsequent ones. In each instance that it's happened with R-33s I get the warning from the first shot and defeat it and it's either the second missile that kills me or a missile that should be dead keeps tracking with no warning.
-
37 minutes ago, captain_dalan said:
Weird, are those AI F-14's the old or the new F-14's? Cause the new ones? Cause the new ones won't engage till well inside 30NM.
As for the R-33, this one most certainly showed on my RWR:
This was 5 days ago. I got the warning from the first R-33. I defeated it and turned back in only to get hit by a different one with no warning whatsoever. https://www.twitch.tv/videos/1123656359
Here's another with a tomcat from two days ago. This one is far more boarderline though as I did potentially have the missile in the blind spot. However, I still would have expected the missile to have been pitbull before I started defending and if it was pitbull I would have had indication because it was on my 6 when it hit and I still never got a peep out of the RWR. If the missile was pitbull I still should have had some tone and if it was being guided by the aircraft I would have had a spike from them which I didn't. https://www.twitch.tv/videos/1123615835
-
It's new tomcats as it was happening recently. As for the R-33 they usually show up but not always. I'm trying to see if I can find the VOD that also shows the Tacview but I got slapped at 70 miles by an R-33 without anything but a 31 nails.
20 minutes ago, Raven (Elysian Angel) said:What IronMike is saying, is that it's only HeatBlur's responsibility if the Phoenix doesn't show up on another F-14's RWR.
The FC3 F-15's got the same problem: it just blows up without any warning. That would be ED's job to fix...
Didn't realize the issue is also in the 15 as I don't fly FC3. It's understandable. I was just searching through and not seeing it reported anywhere.
-
It's not happening in any other module. It only happens when flying the tomcat. Next time it happens ill post the video and trackfile. The stealth phoenixes and R-33s are back. I keep continuously getting shot down from 70 miles by AI F-14s and AI Mig-31s without so much as a spike. Just flying along and jester calls a missile inbound. Nothing on the RWR and then you get hit with no warning or like they said you get warning basically as you explode.
It's happened a bunch on stream and it happened as recently as monday. Track files are too large to upload though, so I will see if I can find anything on my recent vods.
-
Happened to me again today.
-
Little update: I think this issue is solely because the gear isn't coming up when in my flight it did. You can see the back pressure on the stick release from the wheels coming up on my flight and see that it represents when the aircraft starts to sink. It's still nose heavy from the gear being out where my control inputs are based on a more tail heavy aircraft. The issue then is why would the gear be coming up when I fly it but not coming up in the track.
-
1
-
-
I'm trying to make a tutorial series on the TF-51. However, any trackfile I watch the gear never gets raised and the aircraft slowly descends into the ground immediately on takeoff. This is the fourth or fifth trackfile I've tried to play back to no avail. Every takeoff they don't raise the gear and immediately crash on takeoff. I know the trackfiles are bad but if I can't even record a pattern it makes getting footage really difficult.
-
1
-
-
I think this was the best play. Being able to roleplay a slightly earlier scenario should definitely be doable. Thank you for the concise response!
-
6
-
-
The issue doesn't appear to present itself while on the ground so it may be related to how terrain is changing in the display. Unfortunately the trackfile is too large to upload but I do have video of the issue being reproduced. While on the ground FPS was normal and terrain mode was operating. As soon as I become airborne my frames start dropping to single digits. Turning off the terrain display immediately restores performance. Putting it back to terrain mode immediately tanked performance again.
-
Yup still there.
-
Would be a cool little spot for help and harrier ops. Maybe even some war birds out of there for some old school coin ops. Would be nice to have.
-
1
-
-
Yes please. It's been a thing for years. My rwr shouldn't be screaming at me from a mig 200 miles away, WHILE I'M INSIDE OF A HANGER!
-
3
-
-
I've had the same issue since release.
-
Not necessarily a bug exactly but if you intend to extinguish a fire in the right engine, left click actuates the right engine and right click actuates the left engine.
Canopy close is also left click down but seat raise or lower is right click down. It's really confusing when these switches are inconsistent.
-
I also have this issue. Missile's tracking on the right track and smashes itself into the water a mile short of the target.
-
This is still broken.
-
+1
In my case I have to alternately flick back and forth between White Hot and Black Hot to try and wake it up which sometimes works. Also any missile or bomb impacts causes my TGP to white out like its over-exposed. I don't know if this is intended behaviour or not. I will try and upload a track later..
It used to have like a bloom effect from the heat of the explosion but it would subside fairly quickly. Even switching between white hot and black hot didn't help for me. I even completely powered down the pod and restarted it to no avail.
-
I was using it on stream like an hour ago and it worked fine.
-
The default settings on the mfds are not correct as well but the target pod is acting like there is a giant cloud in front of it. In this mission it worked ok but took a lot of messing with contrast gain and brightness to get to a usable level in black hot. White hot was completely unusable. After landing and rearming I headed back to the target area and the entire target pod was completely unusable and looked like some kind of cloud was in front if it when it would work and randomly the entire tgp would just go black.
You can see what's happening in this clip it's not allowing me to attach the track file. I added the track file in the link below because it would not let me upload due to a "security token" issue which then asked me to follow a link to report to admin which was broken and asked me to report that to the admin which was the same link.
https://www.dropbox.com/sh/l3k3aub2swtguei/AACGVQcEG8fkI_r7CW5wzx86a?dl=0
-
That is all.
-
1
-
-
modern
-
Yup. Started with the latest update. Even with a rate of decent that you are supposed to have for vertical landing betty wont stop asking for power.
Possible bug and-or weird behavior of the RWR when Fired upon by a MiG-31 with an R-33
in Bugs and Problems
Posted
Nope. Happened a few times today with the Mig-25 as well with R-40's. Beat the first one, then nothing but nails until I explode from a 60 mile shot.