All Activity

open public level (media, old pdf etc) we can access. of coruse, we dont know see real gmt f16 If there is something that makes sense of material, of course dcs players will understand.

Have a cull (DCS Hanger) file system on a storage drive for unused and archived stuff, like liveries and entire modules, w/ a "Deployed" text file in each folder. Takes a few minutes after every update to toss ~ 50 Gigs of don't need. Bowie

It was already set at 0.5, since im in VR and there's no gains beyond that.. Thanks!

This question is somewhat related to a question I had before, but it's new. I'm trying to get used to this Stick for Air Refueling. For now, I have my settings set at Deadzone 3 and Curvature at 10 for both pitch & roll, and I am all over the place. I know this takes practice, but do these settings seem OK? Any suggestions?

Еще одно видео

AI Iron Bomb Release Sequence Issue: All and Four/Half are fine. Pairs: 8(Mk. 82 slicks) + 2 drop tanks - C/L-C - C/L-L - L/Wing+C/L-R/Rear -R/Wing+C/L-R/Forward Asymmetrical - after the third drop, until the final. Please advise. Note: Have not tested the player sequence. Bowie

I have given up on the ESP32. I found a mini-Mega that I am trying to use. I have copied the code from the forum here and used the mega specific code line. In IDE it verifies fine, but when I try and upload it never completes the upload? This is the code that I am trying to load, see attached. Any help here. The DED is turning into my longest and hardest pit upgrade yet. DED Arduino Code for MEGA.pdf

The secret is to enjoy what we've been given...maybe even express a little gratitude that someone has given the fruits of their labor to the community...not to ask for "at least" something else

Please make this a priority. We can't experience the damage model if we can't taxi and get into the air. Thank you!

-Tested with no HMMWV and no T72B/T72BU/T80/T90 (replaced with M113 BTR_D and T-55), UH-60A replaced with UH-1H, removed all infantry class units to see if resolved...no luck. -Tested without Stennis and without Tarawa (all naval assets removed). No luck. It ran longer, but that may just be random chance. -Tested without naval assets and with Mi-28, Ka-50, Mi-24V, Mi-24P replaced with AH-1W; Mi-26 and Ka-27 replaced with UH-1H. Also removed CRAM. No luck. -Tested with the above helicopter changes and naval asset removal, but also replaced RED JF-17, MiG-23MLD, MiG-25PD, MiG-25RBT, MiG-27K, MiG-29A, MiG-29S, MiG-31, Su-24M, Su-25/T/TM, Su-27, Su-30 with F-16; Tu-160, Tu-95 replaced with F-18 SLAM-ERs; Tu-22M replaced with F-4; IL-78M replaced with KC-135 MPRS. No luck.

Here's a quick video I made today. Spitfire, BF 109, FW190 A8 & D9, I16, P51 all behave very similar to the P47. I understand there are probably feature sets that have higher priority than this subject, and I'm aware it's early access. I was thinking after recording the video maybe there can be a compromise where on the carrier deck you navigate the \ F8 menu to get reset to the rear of the deck or something... Usually the airfields have enough space to get forward velocity and steer around, but on carrier decks, no chance. I think that alone is enough to warrant some investigation from the Devs.

Yeah, that's weird. Lmao maybe we will get better simulation in the future.

This is the issue presented in the linked topic. There's no mention of any kind of nose angle in OP's original post. Also that was a reply to a flippant comment. As far as any updates to the A2G radar goes. They are likely very low priority as neither most players nor the real life pilots seemed to like to use it.

First off, I am not the one who marked it as "correct-as-is", that is the ED team who does that. Second, don't send links to try to prove something when the screenshots you just shared are from a document for the other F16 sim. Also, kinda weird how you took screenshots from another doc but linked to another one as if I wouldn't find where you actually grabbed those screenshots. Third off, if you have actual publically available source material that contradicts what is in this sim send it directly to either Nineline or BigNewy. Thank you and have a good day.

I saw some videos and this seems to be promising

Glad you got it figured out. I'm slowly contemplating an upgrade when my retirement kicks in next year. Getting tired of Meta's update screwing the pooch for everyone. Have them locked out for now. Running a 5800x3d quest pro 6950xt with virtual desktop. Happy with the balance of gameplay and visuals but always wanting more J

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.