All Activity

The question is not the R-27ER or ET, even if everybody talking about their compatibility. The point is: the MiG-29 9.12A and B versions, so as the 9.13 only had the R-27R. There were no R-27T for the MiG-29 serial production versions. The longer ER is a way different question, since their length simply did not allow to use the flap. Here is a ukrainan 9.13: Here is a russian MiG-29SMT (which is very far from the 9.12): But the 9.12A and B had no these weapons, or if they would have, that would be only the ER. The T and ET belongs to only the Su-27 family.

Strange. Maybe the keyboard just don't work, I usually do this by mouse clicking.

Hello comrades and sorry for my English. Yesterday I found a performance problem on the map "Cold War - Germany". When I install the S-75 or Kub (for example) on the air defense position on the map (or outside it) - then at a certain point in time and at a certain camera angle the FPS drops. Very much. A jump from 150-180 frames to 40 or even 25 frames. If I turn the camera slightly at a different angle (see screenshots) - the FPS is restored to values of 170-180. Having turned the camera a little - it drops again. After a few minutes - it can recover itself and the performance becomes stable, as if nothing happened ... I added the mission here as an example. I am attaching screenshots. My configuration: AMD Ryzen 7 5800X3D (4,5Ghz), ASrock Fatal1ty x470 Gaming K4, 64Gb DDR4 3200MHz G.Skill RIPJAWS V, Palit RTX4070Ti GamingPro OC, Samsung SSD m.2 970EVO (970 EVO Plus), ARDOR GAMING Infinity 27 (IPS/1080p/165Hz), Windows 11. Please note that in the cockpit, the FPS is stable, even despite the fact that there are a lot of Phantoms on the station. And as soon as I turn on the F7 camera, the performance drops when I look at the SAM system at a certain angle. There are no mods in the mission. The textures are standard. At the same time, sometimes the FPS drop is noticeable immediately after the mission starts, and sometimes you need to restart the mission several times. Sometimes the drop appears immediately, from the start, and sometimes a little later. Simulator settings are on the screenshot. I haven't checked with other units, but there may be similar problems. This hasn't happened before. The game version is the latest. Opened MSI Afterburner - the video card is loaded at all 12G, as always. Temperature - 50-60 degrees. Processor - 60-71 degrees, frequency 4450 (no boost). RAM - load from 45 to 49 gigabytes out of 64. When the above problem occurs - there are no surges in voltage, temperature, hardware load. F-4e (F) - Германия - Фантом Люфтваффе.miz

Keep trying, it’s a lot of trial and error but it’s worth it.

The tutorials don’t follow the current state of the module. They follow real world instructions. BTW closing your oil coolers is probably a bad idea.

Hello, I'm still not able to reproduce your issue on my PC...Everything is working as expected with your settings. I did not see any missing shader in the reshade.log... Could you add also the file ReShadePreset.ini ?

I’m sorry hou might want to contact Heatblur about it. I did not develop the F-14 module.

Gill flutter was in the trailer/intro video.

Have you cycled between low speed and high speed moving targets ? Also make sure there are no hills between you and target ?

Okay, ich sehe jetzt hier keinen Unterschied in den Aussagen. Jeder soll hier mit dem Modul Spaß haben, dass zu ihm passt & mit dem er sich gerne befasst. Können wir uns darauf einigen?

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

Ok great this is super helpful. It sounds like if I want sound to come out of the Pimax headset, I should select “ Headphones 2- Pimax ….” And if so I should be getting sound out of the DMAS speakers AND presumably the headphone jack on the headset itself. This is currently not the case on my headset (I only get sound out of the 3.5mm headphone jack) so something is definitely wrong with the DMAS speakers I installed…I was under the impression the DMAS speakers would show up as a completely different output I need to select (which was wrong). Thank you @Panzerlang

Can you post a new Discord Link? The one you have is no longer active.

Hello. Why do I have 2 seats clipping into each other?

@-Rudel- Is there any update on this at all?

If the pylons are culprit, I have no idea how to reproduce tests.

Well if the AN/ARR-2 antenna can reduce speed by 1 knot, imagine what two large pylons can do.

Thanks for the response. This is a great F-4B track. (F-4E w/ AIM-7E/-9B, sans 20mm ammo) F-4E Goes Stupid.trk Excellent performance, until after the last Enfield 01 kill, at the 28:15 mark. Then, all remaining F-4E's go stupid. Bowie

Is this going to get fixed? For two months now, you can’t tune the radios on the Chinook. Is there a workaround?

THIS IS WHAT I USED TO DO BUT NO LONGER WORKS In a mission with three bandits and me with 6 aim120c I can usually target all three jets and fire on them consecutively. This is how I used to do it select TWS mode set to AUTO let the lead jet get automatically locked in TWS and let the track file populate. At 80 miles i back out of radar and select “ANZEL” and the “AUTO” Back to radar select EXP to expand the view. select RAID from there I can press “S” to toggle through the targets in TWS and fire at will. That method no longer works. When I set it all up similarly, pressing “S” doesn’t toggle to the other contacts. Just stays locked on the lead jet. with the way it is now I manually have to fire on the lead, break lock, lock up no. 2 and repeat for the third jet. I’m pretty sure this is broken unless the procedure has changed.

Any word? @NineLine @BIGNEWY

The problem is that after ADI was introduced on the later 1As, (and it WAS introduced in the 1A first, not the 1D) a lot of older machines already in the field were retrofit (Vought was nice to provide mod kits for a lot of the incremental updates to groups already in-theater, like replacement panels to eliminate the top cowl flaps) so you probably had a some war-weary birdcages out there that received 8W engines once spares were delivered. Unfortunately, that kind of makes figuring out what condition the test aircraft are in a pain because you've got a lot of mismatching of configurations thanks to the various Vought mod kits and field kludges, unless they specifically used aircraft pulled right off the assembly line. 17930 on that site is definitely a 1A by serial number, and the speed they're reporting of ~420mph is consistent with the use of ADI (speed without ADI topped out around 400mph). I don't think the prop affected top speed as much as it did the acceleration and rate of climb, so you can't really tell from airspeed whether it has the toothpick or later paddle prop. Whether or not something is "clean" or not is a problem because we (currently) can't fly in this configuration, unless there's plans to allow us to remove the knuckle pylons in the future (though personally I'd rather just have a Variant added for the 1A).

There's definitely problems with the modelling. Trying to run WEP at full RPM overboosts the engine and causes it to knock. It very much shouldn't be doing that. Also, WEP should be at 2700rpm all the way up, as shown in the actual flight chart, NOT 2550 as in the kneeboard data. The actual flight data shows different blower settings from what the module uses, as well. WEP blower should be neutral below 8000ft, not Low at 5000. Boost is also too low in the kneeboard data, with 57.5in below 8000ft, 59in between 8000-17,000ft, and 59.5 above 17,000. So once again, that kneeboard data is wrong, and if that's what the engine modeling is based off of, then the modeling is incorrect, as well. Which means right now the Corsair isn't able to get all the power from the engine it should be because you can't use rated power settings without killing it.

好的，谢谢

Did it again with Auto Lean and MAP showed at 57" in the F2 view. You'll notice my velocity increased by 2 kts - almost got to M3's 306. null