VikingSail

The issue with that approach (in my case) is that, because I don't own the F5 module, my shop does not show me the upgrade as a 9.9 USD purchase so I cannot select it and proceed with the gift option. Instead I only see the brand new F5 remastered version for 59.99.

I'd like to purchase the upgrade for the 9.9 USD price tag for a friend who already owns a copy of the F5. But I can't see any upgrade option in the shop since I don't own the original F5 module. Is there a way to purchase the upgrade and send it as a gift for my friend somehow?

woah a new low in DCS terrain development history just happened. can we have some explanations?

the issue with the SC module is still prevalent after the update/hotfix patch DCS 2.9.6.58056. disabling the SC module and the dynamic slotting UI becomes usable with a few freezes.

Thank you @Machalot for the detailed explanation. That was very informative! Thank you!

I have one question about something in the changelog: It says "Avionics: Added “runway search” if A/C heading is > 15 deg from the stored runway". What is this and how exactly could we use it? Thank you.

upon further investigation it seems the SuperCarrier module is the culprit in my case. After disabling the SuperCarrier I can leave all the other modules active and the freeze on the slotting menu is minimal.

null@Nazgûl just saw you still testing on Contention. I am experienting the same issue. I can relate to your frustration. EDIT: scratch the conclusion below. check out the actual temporary fix here: Although after some initial testing I have found a temporary solution: You need to disable pretty much every module except the one you want to fly. So keeping 1-2 plane modules and the map the server runs. Join the server, select the faction, click join. It should bring you to the slotting menu. The menu should recover from an initial freeze very quickly - for me the UI becomes responsive within 2 seconds. At this point you can start filtering out the available slots and the slotting menu should stay fine from this point on. Some more caveats I have noticed in my tests: 1. if the Supercarrier module is enabled, upon clicking "join" after selecting a faction, all the slots will **appear* to be joinable even if you don't own the module. Although disabling the Supercarrier module did not help with the freeze issue on very large servers with hundreds of slots and ground units. 2. continuing from the point mentioned above, it seems that the freeze issue depends on two factors: if the server does not have hundreds/thousands of static spawn slots, or if the server doesn't have a lot of ground units, it doesn't not freeze the slotting menu at all. a good example for the second case is Growling Sidewinder - the server has barely any ground units. the slotting menu runs smoothly. examples for the first case are plenty - just join any small server. it's pretty much guaranteed to work. bad examples for the two factors causing the freeze: ECW, Contention, Flashpoint Levant, the Coop. the commonality between these servers is that they run tons of ground units and have hundreds of static slots. 3. judging by the games behaviour, it seems that the freeze is related to the game loading in all the available units from that faction at once - every active unit on the map from planes to ships to ground troops. but this is just a wild guess. I don't have the internal tools to observe the process behaviour to determine what exactly is happening. but the insane RAM usage during the slotting phase made me believe it is the game trying to load in all the units at once. with 64GB of RAM, I'm already using over 52GB of RAM upon joining Contention - before spawning in any vehicle.

The changes look good so far. I love the improvements to the radar screen with its color changed back to its original one and with tons of new improvements. I haven't tested all the weapons yet. But overall I'd say this is a great patch for the Viggen. My only problem is that the dynamic slots feature has been preventing me from joining any medium+ sized MP servers lol.... But that's not a HB issue. xDD I have saved up two screenshots after loading in to the Viggen post-patch just to say thank you: Look how clean and high definition this radar picture is now! Oh and that comma on the altitude index! Muuua! Great job HB and especially lots of thanks to @MYSE1234!

this helped me. thank you! for those who want to remove the old nicknames, simply edit the nickname.lua file under \Saved Games\DCS.openbeta\Config.

The city of Darʿā sits right in the center of the red half-ring road. The city played an important role in the beginning of the Syrian civil war. I think it deserves its own place in the DCS Syria map.

solved. i figured out it is due to the FC3 clickable mod. a possible fix is to replace the clickable.lua script with this one: https://raw.githubusercontent.com/okopanja/CLICKABLE-FC3/fix_radar_slew_conflict_with_prf_mode/Cockpit/Scripts/SYSTEMS/clickable.lua

To reproduce the issue: switch to BVR mode slew the radar disk horizontally by using the "scan zone left" or "scan zone right" keybind keep eyes on the PRF frequency (med/high, or auto/med/high on Soviet planes) notice the PRF frequency will swap between all settings when the scan zone left/right keys are held (even on the F-15C where the radar disc can cover 120° and does not need to be slewed manually). Untitled.mp4 Untitled1.mp4 Expect behaviour: scan zone left/right should only slew the radar disc. PRF frequency should only be changed by using the "Radar Pulse Repeat Frequency Select" key. they should not interfere with each other. This issue has appeared during one of the patches before the F-4 Phantom was released. Possibly from the FC3 texture update patch (can't be 100% sure on that). I've confirmed it with other friends of mine and it is consistent on all of our systems. I'm surprised no one reported it here for this long.

still curious about HB's official stance on the Viggen radar scope color issue thoroughly discussed in the Feb 2024 update feedback thread. like many others, I think the current Viggen radar is a degrade in terms of functionality compared to before the Feb update.

what's more strange is that how come we can mount the dual rack 250kg LS-6 on pylon 2 and 6, but not on inboard pylon 3 and 5 (which is also listed on the picture above)?

I keep noticing the same error popping up and now in even more scenarios. previous it, started with only when "reslotting" i.e. after pressing "BRIEFING" and then "FLY" again without changing the slot. then it started with changing to a Mi-24P slot from any other slot, including from other Mi-24P slots. now it started throwing this error even when connecting to a server with Mi-24P enabled. below is the log file from the last scenario: game crashed when on the loading screen connecting to the server. dcs.log-20240229-231750.zip

I'm not sure. I'm guessing that because I've only seen ED's modules having that feature. Maybe someone can correct me.

that radar scope at launch and how it illuminates the surroundings with its glowing jade-like light. so sexy!

changed from TF-51 to Mi-24P on a multiplayer server. didn't use any Mi-24P slots before. Upon spawning it was an instant crash. dcs.log-20240228-132031.zip

We don't know the placement of the camera. It could be that the camera is placed directly behind the HUD and therefore you can see a lot more than where you would be able to see from a normal sitting position (i.e. leaning against the back of the seat). But the argument from the PoV of the usability of a product still stands. We don't necessarily want everything to be 1:1 accurate. Because it is a game product. It is about making the general audience happy with the implementation of simulating on-board systems.

Yes. From a functionality point of view, the new HUD can make it impossible to read all the necessary symbology at the same time. At certain headings for example, you can't see either of the two bearings because they are too far outside of the HUD. The old one worked better.

this feature might be locked behind the SDK.

I just realised something... the DDD radar display on the RIO seat on board the F-14 actually has a really close color resemblance of the Viggen's old radar scope. Heatblur, just copy the code and give us a hot fix already.

This looks very promising. Thanks to @Schmidtfire for the good find. Hope it gets corrected soon!

I agree with the observations about the EP13. I believe many others would say the same thing too: to better utilise the EP13 sight, the standard procedure has been reducing its brightness to 0 and then adjust the contrast for as long as I can remember. anything above 0 brightness would usually yield a less usable picture. however, even during darker hours, using a higher brightness simply washes out the picture without providing much "gain" to the overall exposure. It is incredibly difficult to create an accurate-to-the-eye image in post-processing when the original medium has significant informational losses. The information is simply not there to work with. Most significantly it is about the compressed color range and the extremely narrow dynamic range compared to human vision. At the end of the day, it is about re-creating the sense of dynamic range - making things accurate by the number (when that number isn't even accurate to start with) will degrade the quality of the module as a product.