All Activity

Well I think I know what the issue was. I put Pimax plays quality to custom and put it at 20% and it was still crystal clear. Which I thought was odd. There was not perceived quality loss at all. Went through the config and noticed the resolution was at at like 1700x1700 per eye. Then put it at 100% and it was at like 3840x3840 per eye. Deleted pimax play and reinstalled. 100% slider was at 2880x2880. ( I used steam VR to check the actual resolution coming through) I guess a corrupted pimax play install was it. Or it thought my OG crystal was the super. Jesus I was going mad. Also, there is an argument to put pimax play and DCS on the CCD1 without the cache. Average FPS was down like 10fps but it was stutter free. Putting it on CCD0 with the VCache had a higher overall fps but there was more stutters. Also, reapplied thermal paste and there is no change in temps. So in conclusion Pimax play had my resolution almost two times higher than what my headset is rated for. A reinstall fixed the issue. And P.S. There was a performance uplift going the AMD 9950X3D. Instead of 90 to 100fps. I was getting 110 to 120. Then when switching too DLAA and DLSS (the new transformer model got rid of the ghosting completely) pinned at 120fps. Thanks everyone who chimed in.

Also, never once did the frame counter say I was GPU bound. It just said CPU Bound Rendering Thread.

If you make one of your waypoints the bullseye, your tdc cursor will tell you the distance and bearing to the bullseye when it is selected as the active waypoint.

Thats 6.16 per rack? If thats the case, 12.32 reaching its top speed of 1.33 takes 220nm in full burner, Which unless you're using unlimited fuel is not only impossible it's not viable. While reaching the top speed with 2 BRM pods and 2 PL-5s takes roughly 40nm with a drag of 23.2 nearly double, and is completely possible. Or reaching the top speed with 2 GB6 SFWs, 2 SD10s & 2 PL-5s with a drag of 27.6 more than double the drag & a higher weight still takes only 40nm. I am ignorant to understanding drag values and how they are presented in game. But seeminlgy, either something is wrong with the SD-10 double racks, or everything else. (These are all in level flight, no diving for profiles or anything)

Well I think I know what the issue was. I put Pimax plays quality to custom and put it at 20% and it was still crystal clear. Which I thought was odd. There was not perceived quality loss at all. Went through the config and noticed the resolution was at at like 1700x1700 per eye. Then put it at 100% and it was at like 3840x3840 per eye. Deleted pimax play and reinstalled. 100% slider was at 2880x2880. ( I used steam VR to check the actual resolution coming through) I guess a corrupted pimax play install was it. Or it thought my OG crystal was the super. Jesus I was going mad. Also, there is an argument to put pimax play and DCS on the CCD1 without the cache. Average FPS was down like 10fps but it was stutter free. Putting it on CCD0 with the VCache had a higher overall fps but there was more stutters. Also, reapplied thermal paste and there is no change in temps. So in conclusion Pimax play had my resolution almost two times higher than what my headset is rated for. A reinstall fixed the issue. And P.S. There was a performance uplift going the AMD 9950X3D. Instead of 90 to 100fps. I was getting 110 to 120. Then when switching too DLAA and DLSS (the new transformer model got rid of the ghosting completely) pinned at 120fps. Thanks everyone who chimed in.

Follow the instructions to create thunderstorms in the first post, and you should see lightning along with it.

Sorry, this one: https://youtu.be/-ofsq675eoA?si=qkGQsigsxyNREBp8

Hi, here https://cmano-db.com/weapon/459/ it is stated that: Laser Target Designator & Ranger (LTD/R) Max Range: 27.8 km @BIGNEWY Then is it in line with your sources and will it be evolved to that?, up to now for buddy lasing the emitter has to be below 8nm. Thanks

That's so weird, I have a some what similar system. I'm am running a b650 board (so no pcie 5 for me) same speed ram as yours with a 9800x3d and an MSI 5090oc and I can tell you that I'm getting 60+fps with everything nearly on and the resolution on the Pimax CL at native. I will say that I'm not running any AA, as it's sharp enough at that resolution. Smooth with no over the port and starboard side stutters.

A few more... 20250725_151637.mp4

Hello, When exporting a .stm of a flight group with custom callsign label/number The .stm embed well the new label/number. But at import, newly created groupe based on .stm doesn't relfect label and number Group exported: Group after import in a new mission: Here is the .miz used to export, and the .miz after import. As well as the .stm (where BO 01/02/03/04 are well seen) Observed with F18 and F16. test_DL_Group_after.miz test_DL_Group_before.miz I would assume that all are generated at groupe creation.If yes, why include them in the .stm ? Maybe use the one in the .stm if numbers are free, then generate if number are already taken ? EDIT: I didn't see at first glance that STN is also not the one exported.

TOR M2 can inherit all sensor from TOR and PANTSIR from TUNGUSKA they are kind of the same in DCS except for better performance. this is very disappointing considering that while they were a standalone mod they worked perfectly.... imho it should be fixed asap.

Early Access... for ever...

Yes, is the most unstable helicopter of DCS yet it has an advanced stability system.

Nearly to the end of this fantastic campaign in the P-47, and something that makes these campaigns standout is the historical accuracy and level of detail. For instance, prior to mission 11, I had never heard of operation Frantic (despite many documentaries and much WW2 reading over many years) - just done a read through on Wikipedia (https://en.wikipedia.org/wiki/Operation_Frantic) and wow, what an interesting operation. Run bombers and their escorts on round trips from UK to USSR and Italy then back to the UK. Its also interesting to read about the relations between the US and USSR at this time and the growing unease between the 2 being a sign of things to come in the cold war. Not just a campaign, but also a fascinating history lesson, superb . P.S. I find the info from Dogday upon return - namely the runway in use, to be really helpful. After over an hour airborne its easy to forget which runway you took off from.

Strange. I had my track go in super slow motion. And what came out of the RPG was the same artillery shell as always. And this was like a week ago. I'll have to try again. Explosion is still to large, an RPG though. But the graphical effects doesn't necessarily correlate to the damage simulation. But it looks odd that both RPG and 80mm mortar has more or less the same explosion size of a mk82.

The insurgent one also fires the PG-15V model: If you change .trk to .miz you'll get the mission file, confirming I used the insurgent one. PG-16V_Insurgent_model.trk

The new version from 07/23/2025 is missing the chapter about AN/AAQ-28 LITENING TGP from before.

When the work on the chopper is complete, you can approach the other vendors like Heatblur or Magnitude 3. They might give you a job. Mike Force Team

I'll buy it as soon as it's available. And good luck with your work!

what about make it from the f10 menu talk to the ground crew to lower the elevator when the player is on the elevator

What keeps me from doing it is the necessary infrastructure update (mobo+ram) that comes with it. If it was the swap of the CPU, I would certainly do it. It is just a gut feeling, but I don’t really want to switch to DDR5. And if I’m honest to myself, an upgrade isn’t really economically justifiable.

The Warthog is mapped automatically to all correct switches, and according to your screens all seems correct. APU on-off is the correct binding as the Warthog has two and three position switches where only one side is electrically connected. Two sides for 3 position switches of course. Throttles all the way back, not in cut-off, is idle. You can even see button 29 and 30 are correctly bound. When you move the throttles out of cut off, you are in idle. Somewhere in the general settings, there is an option called sync with HOTAS at mission start. Test it both on and off you see if your experience gets better. Sent from my SM-A536B using Tapatalk

Here you go. I have a few but this was the last one after I ran the repair. dcs.log-20250821-202548.zip Thanks for the help by the way!!

I hadn't seen this mentioned yet, but I actually visited EAA this year. Easy enough for me to do, since I'm a 15 minute drive away. Some of what I've recorded... One thing I can say, is that the F-35 is extremely LOUD. I never heard anything like it before, and I've seen plenty. 20250725_145316.mp4