All Activity

That's a crazy value, sorry. I have the IPD set to 62 in DCS, if I remember correctly, and it actually looks good, and in most modules the scale is fine (although there are exceptions, like the F-86, which has an oversized cockpit interior). The MiG-29, on the other hand, has an okay size. While we can set it to 85 and it might work, it's a completely unrealistic level.

You should set your own RL IPD value, otherwise you're distorting object sizes perception making the view unreal. But it's ok if you just like the effect and accept it. Even such extreme unrealistic value of 85mm should not affect the visor though which is wider than that. So that points to the incorrect implementation of the visor view if one side glass width is calculated differently than the other, ie. not symmetrical. Ex. right eye view point is correct RX=centerX+IPD/2 while left one LX=centerX-IPD is not. Just example of how such error could look like. Also make sure you're not using any mods, especially the one for the visor!

Thank you, but I know how to do the setup because I have been flying with this setup for years without any problems. I contacted Pimax support and explained the problem. Pimax recognizes the problem and recommends: Try turning off sharpening in Pimax Play. This is a known issue, which may conflict with the sharpening feature in the game. I will go back to the previous Pimax-Play version V1.40.1.114_202506171545 and hope that this will solve the problem!

This looks very much like a bug with the new missile API. I have noticed as well that all you need to do is roll and pull a little and the R-27 just lost all abilitly to guide, and no chaff is needed at all. Especially if anykind of hard roll is intruduced. ColdClaws report and yours shows the same exact bug. Hope this gets fixed soon, since this is some warthunder levels of "just roll and the missile misses" kind of bug.

It is "just" the known issue. As explained in the threads, the exact way how the bug surfaces on your end changes with each update (for technical reasons - its called "Undefined Behavior").

fixed internally for future update thank you

There is only one switch to control 6 weapon stations which are divided in inner and outer. The meaning of these stations is relative and depends on present ocuppancy of stations. Yhey also have reverse fire ordering rule. You may also affect it withel 1 komplet/0.5komplet switch. Also air/ground switch might also play role in mixed A/A A/G roles depending on what kind of load is hanged. Still I do not see the way to toggle beetween R and T except that you hang only R and T, in which firing order rule would allow you to switch between them with inner/outer switch.

I ran this script on my server, and they look amazing. Thanks for your work!

Something I've noticed is the gyro cage button is illuminated in red on manual start even 5mins+ after starting and completing the startup sequence. I pressed it in flight and it did nothing but then a minute later it all came alive... very strange

According to the manual, page 24, item number 26, this switch has no function, which then would explain why it's not mappable in the settings.

I'm bugging the ED guys again, it looks like this is happening to other campaigns too. And we're on the same boat, we've no idea how to troubleshoot this one, because it's not something we have any control over it.

If it helps, you have save and load functions, you bind one, save and load on the others. Load translates well also on the Flanker, but you need to bind the Nose Wheel Steering as well

No not at all it’s completely innacurate. There is real manual, I can link it in a bit

I was also confused why Wags set target hieggt in his AG video.

Maybe it's not obvious to you, but MiG-29 is not compatible with ILS. If you want to use PRMG/RSBN you have to put and configure the units at the airport you want to land at. Only some Caucasus (russian side) and Cold War Germany (GDR) airports have set PRMG/RSBN by default.

Same here. I couldn't investigate or reproduce it yet but I had the same happening during my last sortie yesterday. Target was shot down before I really had a chance but from ~80 to ~20 miles closing in I wasn't able to get a solid lock. Most of the time pressing TDC nothing happened.

Check again your license.

При игре в ВР (Oculus quest 3s) наблюдаю баг с текстурой. Манипуляции с настройками ничего не дают. Стим версия игры

Всем доброе утро. Когда выйдет обновление,киньте сюда ссылку пожалуйста.

Hey, thanks for the track. I noticed a number of things wrong with your track. The DTC, airbase RSBN set up and procedures for the final had errors. I suggest checking out Wags navigation video and reviewing the RSBN setup guide. As far as the Command Bars, the procedures you followed would not have activated them. They should only work for APPROACH and AUTOMATIC landing modes, and those are not included yet. Thanks.

I have the F-16D (only Blk 50 + 52 without spine) working very well. I deleted some features from original release and matched functions and so on with stock F-16C files. Now I have a problem with the avionics. when doing the autostart procedure, and then turning AG mode on, the CCIP doesn´t work. It is offset, or frozen, so that you can´t fire any weapon. When starting a mission with turbines on, it works. But only until you land, shut down and restart. Anyone know a solution? Or any idea wich files needs to modified here?

Thats how Viggen works, it uses barometric settings for weapon deployments, how the MIG functions I dont know. But they are both cold-war jets, perhaps it was common back then?

Correct as is? I don't understand. Can I ask for feedback on why this is good? Command bars do not move in the current version. That's not correct.