skywalker22

its pointless to talk here, this plane won't get released for a couple of years.

Who did the new RSBN, Magnitude team? Mine version was complete and accurate (based on airports avilable at that time), this one is not. @Molnija1985 use mine, if you need the correct rsbn navigation.

Althoguh it looks better, it does break IC. So no thx.

What do you mean it always scans the ground? This can't be, radar doesn't know what the ground is. It is scanning what the radar sees in it's the gimbal limits (120deg vertical and horizontal), and no matter where the aircraft is pointing. And based on what is sees, it maps on the MFD. If sky, it's all black, same as the sea, all else has some different gray color variations. The question is where is the radar pointed when in Ground mode?! In A2A you can manually set where does it look, by changing elevation, but in the A2G? Is it pointed straight ahead, is it level with the aircraft, or is it pointing downwards, towards the ground, if so whats the angle (based on level flight, or based on aircraft direction) - before applying any filters? Maybe @RogueSpecterGaming can exapin in more professional way.

Oh, my bad, don't know how did I get this mixed up? I didn't use the harms in a long time

From air to ground. It's also "Air to Air".

In HAD mode with HTS pod, it indeed does find it's target, but always precision factor PGM goes straight to max accuract (5) and it drops from 5 to 2, and stays at 2. The harm still finds the target with pin point precision. There must be something wrong with F-16 HARM system, and how it shows up the precision number. a2g_harm_accuracy_test_2.miz Not sure which fault is it, but it seems thats on F-16 side and its HTS system. And it's the same with any radar that HTS is detecting.

LOL, never seen, actually not seen it in this kind of situation Glad you found it back.

hmmmmm.... I guess 10950X3D

What is that "hump" under the cockpit?

IRL there is no button to reset, so I think we won't get one either.

How often failures occur IRL? I know a lot depends on maintenance, but still, some random failures which you can't predict. F-16 is pretty robust and very perfected aircraft, so I would guess random failures are very very rare.

Please, can ED fix it?

Indeed, VR is next level. I have Quest PRO, but still for some more serious flying I still use TrackIR, and thats because of head turning. I just can't turn as much or as fast or even that often in VR as with TrackIR. Else, experience in VR is stunning indeed. The only complaint is that the graphics are still not as sharp in VR yet. I have VR for almost 3 years now, constantly trying to tweak and use any kind of trick there is, but still missing that image sharpness which we can have with a 2d monitor. Maybe this vr headset that I use (or any other which are available atm), are just not good enough yet. But anyway, user experience is another level. I also want to point out that I drive car racing sims (Le Mans Ultimate atm), where the images seems to be way sharper and clearer then in DCS, and also the whole experience seems to be better just because of that. And with the same VR settings for both games (in openXR toolkit and Oculus Try Tool). In LMU I just can't drive cars in 2d anymore. Anyway, enjoy VR, I know love it.

indeed. So that's why you don't implement it (joke).

Yee, but not like the ones OP proposed Aside weapons random failure (released missiles/rockets not firing, bombs not expolding), would be also good to have radom failures on aircrafts them selfs. There in a feature in the optinos to turn on/off radom failures, but in reality I didn't encounter any so far on any of it.

So we will get B version, the title it's surely not a typo.

This is definitely a C. The main difference among both of them is, that C has 2 cannons on each wing, while B has only one. C would also come in handy, because it has additionally 4 racks for rockets or smaller bombs on both wings.

The stats do not count the multiplayer time, so they are irrelevant. I fly 90% of the time online.

Would be a great addition to the WWII environment. I found these airports on Solomon Islands and Bougainville island of Papua New Guinea: Airports of Solomon islands in order from south to nord with coordinates: 1. Santa Ana -10.84827, 162.45435 2. Tahaworo -10.67602, 162.20512 3. Kirakira: -10.44888, 161.89715 4. Ulawa: -9.86054, 161.97963 5. Marau: -9.86169, 160.82584 6. Parasi: -9.64161, 161.42555 7. Honiara Int.:-9.42827, 160.05417 8. Afutara: -9.19117, 160.94912 9. Yandina: -9.09368, 159.21951 10. Atoifi: -8.873263, 161.011366 11. Gwaunaruu: -8.70248, 160.68176 12. Manaoba: -8.32492, 160.80042 13. Gatokae: -8.73842, 158.20271 14. Seghe: -8.57839, 157.87550 15. Batuna: -8.56239, 158.11918 16. Viru Harbour: -8.50760, 157.68889 17. Munda: -8.32738, 157.26109 18. Ramata: -8.1681, 157.64238 19. Fera: -8.10683, 159.57716 20. Suavanao: -7.58531, 158.73117 21. Ringi Cove: -8.12517, 157.14315 22. Nusatupe: -8.09876, 156.86427 23. Kukudu: -8.026393, 156.947916 24. Barakoma: -7.91154, 156.70568 25. Geva: -7.57590, 156.59719 26. Kagau: -7.32965, 157.58447 27. Mono: -7.41522, 155.56666 28. Ballale: -7.41522, 155.56666 29. Choiseul bay: -6.71170, 156.39611 Airports of Papua New Guinea (whats holding up with the Solomon islands): 30. Buin: -6.73135, 155.68408 31. Tonu: -6.65569, 155.43216 32. Aropa: -6.30552, 155.72805 33. Buka: -5.42218, 154.67290

In VR? If not in VR, then is something wrong with your configuration. But it's still very strange that there is such a huge difference between these 2 maps. Do you have any other map, if so, how is the fps there? Which 14th gen do you have btw? I have the same gpu as you do, but I have amd 9800x3d, and I have no issues what so ever. Also in VR, locked on 72fps. And I'm running undervolted gpu with settings 0.925mV @ 2600MHz, and memory clock +800Mhz.

waiting... I doubt this will salve the issue we are facing here. I have the same issue as OP does, in VR on on 2d monitor. Although the picture is more clearer on the monitor then on VR, and using exactly the same graphics settings. The plane at cca 500-1000m away from me, seem like its all black, it looses on the colors, and its shape as well. I kind of excepted, thats the way it just is. But now when someone brough this up, seems that we have to dig a bit deeper.

Thats the most you can do atm unfortunatelly. Just put the ILS lines at the end of the beacon.lua file, and send the file to others. Don't forget to make a backup copy of the original file copy as well. Modifying that file will surely break IC in most of the other servers, but you can set your own server up without the IC. It's not a hard task to do.

Here it is all explained.