Leaderboard

Thank you Ralfidude

I have some reason to believe that a video will be arriving within the next 12 or so hours.

I've been on work related journey for two weeks. I just got home (like 4h ago) Anyway, In those hours I started working on BA-52 Vyuga ELINT pod, and then the KKR-1

ASC DCS: C-130J "Hercules", startup.

Welcome to the update Vietnam War Vessels 2.0.2! This update brings a few changes with it: First, the USS Enterprise got support for lights at night. Second, the USS Bon Homme Richard and Generic Essex carriers with SCB125 upgrade got updated parking positions, so planes drive in reverse to the parking. Unfortunately the result is not always great - some positions the planes wiggle for and back. We're working on further improvements to this, but with the carrier plugin gone from ModelViewer it's quite some work. Third, the livery names were normalized and start with the ship designation in brackets (e.g. (DD-728)). The update only contains the changed assets and not the complete mod. You need to install Vietnam War Vessels 2.0.0, then update to Vietnam War Vessels 2.0.1, and finally this update Vietnam War Vessels 2.0.2 can be installed. https://github.com/tspindler-cms/tetet-vwv/releases Alternate download on Google Drive: https://drive.google.com/drive/folders/1XHQWl6aq5nPYAeLnRnSViTqPBNsMcx7u?usp=drive_link Enjoy! TeTeT

Hehe I totally get your frustration. It's like all normal polite behavior, goes down the drain as soon as people set foot in the magically digital world called "internet". Just let it slide.. There's plenty of stuff in life worth getting agitated about, this isn't one of them.

It's because the assets in my mod packs doesn't have a Level Of Detail (LOD) configuration. Using this technique the models will be replaced with ones with much less polygons the further away they are. Without LODs your computer will have to calculate the max poly version of the asset regardless of the distance to you. My core DCS assets all have LODs, and I'm currently adding it to the mod packs also, but it'll take a while before it will be done to all of them.

The big wing in flight. 15 spitfires and 6 hurricanes. The view watching them all take off was amazing. Unfortunately I did not video it!

Quick update. I have a team to help with EFM and cockpit model. The A.I. model and FM is coming along nicely.

On behalf of all those people, we say thanks if you have taken the time to come on these forums and help someone out, we at ED certainly appreciate it!

I did see Baltic Dragon flying the C-130J and I think someone was filming, but it was probably for that person's YouTube channel, not Baltic's or ED's. There was also someone from ED there with Baltic, I forget his name, but he wasn't really there to represent as much as to be on hand. Expo was 90% racing, 7% flight simming, and 3% VR, to give you an idea why there is not much footage for the flight sim side. There was only one flight sim cockpit, and that was the Airbus one. There were no other flight sim cockpits, only 1 rig. All the other flight sims were tabletop with HOTAS. And yes, the C-130J was in an area like a LAN party, but that was OK. I myself probably would have filmed more, but I had my son in tow and had to keep an eye on him which wouldn't make for good video footage. v6, boNes Baltic Dragon at 01:26:50!

I had the same problem ending up outside the cockpit. Try scanning your whole room by turning left / right / up / down with your headset on and then recenter VR and then start flying. That helped me to stay within the cockpit (even on a motion rig). Seems like Pimax is adapting tracking / positioning when capturing new objects in the room. Therefore it seems mandatory to make a scanning process before flying...

I'd certainly fancy a Westland Lynx (surely there's a place in DCS for the world's "fastest" helo)(also, DCS could do with some more non-US western modules) But I'd definitely also buy the CH-53 if it were available. With the Hook and Herc, DCS is focussing more and more on cargo hauling in their sim, so the Stallion would be a great addition in that respect

I ONLY have sharpness set in Pimax Play. I turned it to 0 in DCS and in mbucchia's QV. Seems to work great that way.

Currently, ED has been one of the best if not THE best (I don't own all modules) in the sound department in fly-bys. The Viper and the Hornet at the right volume levels are brutal, so I'd say it is in good hands. I hope they do it well.

First images from Duxford Battle of Britain airshow.

Interesting...to ED, the team making the map and therefore the arbiters of what Early Access is "supposed to be", early access is a way for you to access a product before it's finished. The End. What you describe has no relevance to how a map or aircraft is built...that's just not how development works/progresses. So again, you have the option to wait until later and experience the completed product, or access early and complain that you're experiencing it early...as that seems to be how some of you operate.

Maybe this is old news, but why does Pimax want to know my location, where my PC is at, at all times when I turn my PC on? The installed Pimax software literary checks my location every single minute my PC is on and online. Every single minute. Why? I came over this just by accident and have now turned off location services from Windows for the time being. I have checked the history for this for the last week now, and only Pimax is listed as a app that checks my location. And it checks this every single minute. Waste of resources, and there's a privacy concern in this too I think. @Calvin.Pimax Why do you need to know this? And why check it for every minute that passes?

Sorry i use an online translator. Hi If there is something that annoys me, it’s when someone asks for help in the style "Please, i need help" and that responses are given (good or bad), that the same person, who regularly returns to the forum, does not respond even like "thank you, I look at that and come back to you" and well it annoys me to the highest degree. Of course, it may be that the person has barriers but if you click on the name of this person and see that they have come several times to the forum.... Have a good day Christian

BA-52 "Wyuga" - ELINT pod for Su-22, with the "Lutch" indicator. I made it so when you equip the Wyuga, the TV in cockpit gets replaced by the screen for KH-58 and 25MPU targeting. Now comes the fun part - coding the sead indicator and logic using Su-25A avionics

Thank you for your insights and special thanks to Actium for having done the work to actually look into it. That answered my question. Yes, it does raise further questions, like... why? But lets not get carried away.

I’ve updated my original post to include the issues with the Pimax during night missions – it’s not quite perfect after all.

After several weeks of testing the Pimax Super, I’d like to share my impressions. First of all: my setup consists of a full cockpit mounted on a motion platform – which makes tracking especially challenging. Some of my observations may therefore not fully apply to a “normal” desk setup. 1) Setup with Pimax Play In short: absolutely straightforward and without issues. 2) Headstrap The already much-criticized tiny screws are indeed a bit of a joke. On top of that, the headstrap positioning is unfortunate, since its front edge overlaps with the face gasket. Tightening the strap puts more pressure on the gasket than on my head – not a workable solution. Workaround: By chance, I found out that mounting the strap underneath the face gasket works perfectly. This does not compromise the secure fit or the light seal in any way, but the strap now sits firmly on my forehead and provides solid support. 3) Setup for DCS With Pimax Play alone, performance is underwhelming even with QV settings. Thanks to Tally’s brilliant video on setting up the Super with QV Companion, I now get excellent results – limited to 72 Hz though. I almost never reach 90 Hz in complex missions, but 72 Hz are rock-solid, except during missions with heavily populated airports. Important: After every Pimax update, QV Companion must be reinstalled. Using the OpenXR API Layers GUI, always double-check that the right VR APIs are enabled (e.g., QV Companion) and others (like OpenXR Toolkit) are disabled. 4) Image Quality The resolution is simply stunning – even the tiniest cockpit labels are perfectly readable. Colors look vibrant, and night flying is very convincing. When it comes to Foveated Rendering, the size of the high-resolution area is crucial. If set too small, you’ll notice quality drops in your peripheral vision, especially at night with ground lights. Personally, I prefer flying "only" at 72 Hz with a larger FR zone, which feels much more natural. 5) Tracking This is where the Super struggles most. From the start, inside-out tracking was unstable for me: incorrect positioning, jittering in the cockpit, and especially deteriorating stability during long sessions. In my case, the cockpit itself blocks 40–50% of the headset’s visible tracking area. Combined with the motion platform movement, the Super must only rely on the static room environment. My Reverb G2, by the way, never had issues with this. What actually happened: As long as I was looking straight ahead, tracking was somewhat stable. But whenever I turned my head – left, right, or especially backwards – the headset lost orientation and tracking broke down completely. QR codes on the front walls helped a little, but once I looked away from them, chaos returned. After longer sessions, the problem got even worse. The solution: I placed QR codes not only in front but also to the sides and behind me (my platform stands in a corner of the room). Suddenly, the headset tracked much better while turning around. I also suspended QR codes from the ceiling in front of the cockpit, so the headset can pick them up just 1 m away instead of several meters further out. Another crucial step: Before flying, I always scan the entire room with the headset once. Only after that do I recenter VR or calibrate motion compensation. If the headset discovers new QR codes during flight (e.g., when turning around), it seems to re-calibrate mid-air, which in combination with motion compensation led to complete chaos. Since following this procedure, my tracking has been solid and jitter-free. Tracking summary: Place as many QR codes as possible on walls (also sides and rear), and even hang some from the ceiling, close to the seat position. Before each flight, scan the whole room (left/right, up/down). Only then recenter VR and calibrate motion compensation if needed. 6) Mura Effect Until recently, I didn’t even know what “Mura” was. Now I can identify it: a slight “smearing” effect, noticeable when I look at white clouds while my pupils are focused on the near range. But honestly: in real flying, this doesn’t matter to me. When looking into the distance, I can’t see it at all. When focusing on cockpit panels, the busy background of instruments masks it completely. It’s comparable to driving on the German Autobahn with a dirty pair of glasses at 250 km/h (which I actually do every day). In theory, there’s a smear on the lens, but in practice you’ll never notice it – your eyes are focused elsewhere. Conclusion After solving my tracking issues, I’m very impressed with the Pimax Super. Resolution, colors, stability – fantastic! Despite the (for me solved) weaknesses in the headstrap and tracking, I would buy it again without hesitation. A quick addendum – the Pimax Super does seem to have a (software) issue, there are a few problems at night. My tests above were all done in sufficiently bright dawn conditions, which is why I didn’t notice it earlier. Still, I was able to make a bit of progress:

Hey guys - quick update... I have now extensively tested the issues and adjustment options in a night mission (Syria, June, 4 a.m.) and a dawn mission (Syria, June, 04:15–04:30 a.m.): Problems: HALO around bright objects, especially the aircraft in external view Indefinable dark mass from the horizon downward; the transition from the stars over the horizon to the ground is not a clear line, but a constantly shifting “something” Partial “blackout”: when rotating the external view of the jet, brightness suddenly dims completely (across everything); when I then switch into the cockpit, everything is pitch black and the headset gradually brightens again Chromatic Aberration at sunrise / clouds, as described at the beginning of the thread Adjustment options: Contrast & Brightness in PP Local Dimming in PP Gamma in DCS Modifying the profile.json file as described by missioncmdr Upfront, everything that doesn’t work or has no effect: Problems: HALO does not go away, no matter what I do Horizon-to-ground transition remains undefinable Blackouts are still present Adjustment options: 2. Local Dimming in PP makes no difference 4. Modifying the profile.json (simply adding the line with the value, as it is not there initially) causes changes, but in my view nothing that Brightness couldn’t also achieve The only progress so far: Problem: 4. The Chromatic Aberration at sunrise or sunset on the horizon and in the clouds can be removed. Workaround: Set Brightness in PP to -2 and Gamma (previously 1.8 for me) to 2.8 (!). This results in beautifully smooth transitions without artifacts. I tried calibrating the correct brightness against the stars: everything I can see at B=0 and G=1.8, I can also see again at B=-2 and G=2.8. The problem then is with daytime missions: here, with B=-2, Gamma needs to be set to about 2.2–2.4, otherwise it looks too bright. You can fine-tune this a bit by setting Contrast to -2. Then Gamma can stay at 2.8 without affecting nighttime visuals, and during the day you get roughly the same brightness, although the colors appear a little more muted. On the other hand, Gamma can be changed during flight (for day/night missions). So – currently I’m using: In PP: Brightness -2 Contrast -2 In DCS: Gamma 2.8 Fun fact: If Pimax Play is completely closed and restarted, you still get the Chromatic Aberration despite Brightness -2 and Gamma 2.8. I need to briefly move the Brightness slider in PP, set it back to -2, hit Apply, and then the setting works again. This seems to be another bug. @Calvin.Pimax – please have your team take a look at this. It should all be solvable!

The answers found there are from us, thanks.

Yup! They couldnt even test how it would perform against active missiles. And its not like modern RWRs are amazing in this regard, they can give you seconds of warning time at the best of times. Seems like there is a specific SARH warning, but this isnt completely reliable either: https://www.digitalcombatsimulator.com/en/news/2025-07-12/ Tbh I think its pretty cool to have this kind of detail modelled. Already like the attention of detail in the F4, and looks like ED is also stepping it up!

That’s what I got from it as well. Not that it is a problem: it is a system designed to face the threats of that era. It would only need to be careful when facing F-14s (and DCS can’t replicate the Phoenix’s specific guidance anyway so who knows how it would behave).

Damage models: Most of them are FUBAR. I don't know if it's to be player friendly that way players can get away with more to benefit game play. I have personally put hellfires, GBU's into a hind and it shrugged it off. Tricker has tons of videos of him hitting helicopters with multiple 25mm from a Bradley. wow what a great segue. Weapon Damage: A burst of 25mm from the above example would wreck any aircraft, especially a helicopter. I proved that anything below a 30mm rarely damages anything past 4,500ft in my SA-6 thread. How I conducted my test: Using the previous known range of 4,500ft that was the constant. I started each test with a Bradley to engage with its 25mm(since it doesn't have AP/HE in DCS which should be fixed since the LAV does...) This is a good control to start with. - a common issue, the AI shooter would think a helicopter was destroyed and would stop engaging. This is after many rounds hitting target. - I would place the helicopter on the ground as a cold start(meaning they have to start up to get airborne) right above the 4,500ft mark so around 4,520ft. And run the editor. If the helicopter survived the 25mm event, I brought it within 4,500ft. - IF the 25mm was able to destroy the helicopter that was the end of the test, move on to the next helicopter. If not, I replaced the bradley with a common 30mm unit like a BMP-2, BTR-82A, and a BMPT for faster 30mm engagements. Same method, above 4,500ft, within 4,500ft. - IF the helicopter survived the 30mm test. I moved on to a 120mm test from an Abrams or Challenger II. That's where I stopped, no offense but the Russian 125mm tanks in the game are B.S so I didn't use them (prior master gunner, fight me). Test 1: CH-47F Survived all 25mm, 30mm and 120mm engagements, took off and flew away, even with damaged rotors. Truly amazing. Test 2: AH-64D Destroyed within a few bursts of 25mm from above 4,500ft. Test stopped. Test 3: Ka-50 III 25mm destroyed it right before take off above 4,500ft. Skipped straight to 120mm, it took 22 hits to destroy it, last hit was while it was airborne. Test 4: Mi-8 25mm above 4,500ft stopped engaging because it thought the AI was dead. Was able to destroy it within 4,500ft. 30mm above 4,500ft took it out within a few burst. Test stopped. Test 5: Mi-24P Survived all 25mm & 30mm engagements. 120mm needed 7 hits to destroy it. Test 5: OH-58D Survived all 25mm & 30mm engagements. Survived the 120mm above 4,500ft engagement and took off. 120mm within 4,500ft it almost took off but after numerous .50cal and 120mm hits it was finally destroyed. Test 6: SA342 25mm destroyed it above 4,500ft within a few bursts. Test stopped. Test 7: UH-1 25mm destroyed it above 4,500ft within a few bursts. Test stopped. CH-47 vs 25mm above 4,500ft.trk CH-47 vs 25mm within 4,500ft.trk CH-47 vs 30mm above 4,500ft.trk CH-47 vs 30mm within 4,500ft.trk CH-47 vs 120mm above 4,500ft.trk AH-64 vs 25mm above 4,500ft.trk Ka-50 vs 25mm above 4,500ft.trk Ka-50 vs 120mm above 4,500ft(22 hits to kill).trk Mi-8 vs 25mm above 4,500ft.trk Mi-8 vs 25mm within 4,500ft.trk Mi-8 vs 30mm above 4,500ft.trk Mi-24P vs 25mm above 4,500ft.trk Mi-24P vs 25mm within 4,500ft.trk Mi-24P vs 30mm within 4,500ft.trk Mi-24P vs 120mm above 4,500ft(7hits to kill).trk OH-58 vs 120mm above 4,500ft.trk OH-58 vs 120mm within 4,500ft.trk SA342 vs 25mm above 4,500ft.trk UH-1h vs 25mm above 4,500ft.trk

It is true that planning a mission even just for one’s own flight, let alone for several, and thinking about the bigger picture is not to everyone’s taste, and it limits the number of players interested in the campaign. On the other hand, it has been nice to see that there is interest in this as well.

A-4E-C: Main Tires Coefficient of Friction The Differential Breaking/Nose Wheel Castering is much improved. Great work, DevComm. Wondering if the Tire Friction Coefficient shouldn't be a little higher though, maybe 20-30%. Seems to want to skid around the flight deck at just a bit over pedestrian speeds. Not unmanageable, once the envelope is understood. Just seems a little fussy, especially when maneuvering w/ Differential Breaking/Nose Wheel Castering in tight spots, lacking the tow-bar guidance from the deck crew. Great li'l Scooter. Bowie

ChatGPT and other LLMs are a fantastic tool, but are not a replacement for doing actual research. I personally don't find it overly productive to just copypaste AI-written text on online forums, especially when it's not cited.

null

OK, finally got it. @Bowie was indeed onto something In my previous test I didn't use wind and the carrier did not move - logically, to test just the cat shot speed. It didn't show anything unusual. All cats same speed. But after taking another shot (sic!) with Bowie's settings: carrier speed 18kts into the 15kts wind I was able to confirm the bug on unmodded DCS. @Silhou Please check the tracks. Cat #3 on CV-59 is indeed slower about 10kts in these conditions - it makes fully loaded S-3B tanker or F-14A AI sink just a bit - but they can manage fine. CV-59 cat#3 F-14A.miz CV-59 cat#3 S-3B tanker.trk

Not just incomplete, but broken. I have a small group of friends that play on my private server and VOIP hasn't worked for a number of us since its release. I honestly don't understand how a single guy (ciribob) can code, test, release and maintain a custom solution (SRS) for all these years and ED cannot (or won't). As far as I'm concerned, it's a choice. Like many "features" they release, VOIP is an MVP (minimally viable product) with emphasis on Minimal. This approach creates technical and feature debt that often never gets addressed. In the case of VOIP, at least we have a working, feature rich solution called SRS. Save yourself a headache. Install SRS from GitHub and don't look back.

The guy who taught you how to document a bug… well done

Something's off with the Sim Gaming footage. Either they're just short fragments like the one in the video above, recorded rather by accident, or they're just some similar-looking photos. Hello team?! Didn't any DCS fans go there and film a 5-minute flight video of at least a mission?

Sidewinder issue fixed, available with next build.

The crew of the AI MH-60 has been re-assigned Still very early WIP but she'll fit right in

Ltterally just finished to play The Kerman Campaign from Ground Pounder and all work good for me, I've a lot of fun

Yes it’s awesome