All Activity

Its's known issue that currenthill has confirmed elsewhere.

I hope that current model of trasporting troops works here, but Im not 100% sure, I asked it too but I didnt recive the answer yet.

My issue was with the AI choking on setting up attack on enemy aircraft. When I put "weapons hold" and "ignore threats" they flew just fine. Everything still falls apart without very, very tight handholding. The AI had to scramble. Cold start, taxi, take off and climb to intercept. It seems the AI went into attack mode almost immediately after take off and choked on it.

I built a new system for playing DCS in VR which incudes an RTX 5070 Ti OC graphics card. When flying in the F16 and there are clouds/haze in the background, I find the HUD colors to be washed out and difficult to see. I've played with the Gamma setting (currently at 1.3) and while it helps, it really darkens everything else. Are there any other settings in VR that can address this issue?

Agree, but people do it because they like to do it or just because they can. I don't mind, not going to use it, but don't mind someone else having fun with it.

I wanted to test the corsair after the update that improved the flight model(no not yesterday's patch, the one before that) I set up an enemy unknown. Random German ace aircraft would show up. Typical with my luck i got the 109 twice, the first round was in many ways the best one. 10 minute long dogfight. I could have won it if I was a better shot. Second round, managed to get behind it, and used the Corsair AIs playbook, just hold in the trigger and hope to hit. And I did. Took out the radiator. Got a few more hits in. The 3rd round I got an Anton(which i somehow imagined was a Dora until I got very close. The AI Anton is useless, and even with my terrible shooting, it was never much in doubt what would happen.

I wanted to test the corsair after the update that improved the flight model(no not yesterday's patch, the one before that) I set up an enemy unknown. Random German ace aircraft would show up. Typical with my luck i got the 109 twice, the first round was in many ways the best one. 10 minute long dogfight. I could have won it if I was a better shot. Second round, managed to get behind it, and used the Corsair AIs playbook, just hold in the trigger and hope to hit. And I did. Took out the radiator. Got a few more hits in. The 3rd round I got an Anton(which i somehow imagined was a Dora until I got very close. The AI Anton is useless, and even with my terrible shooting, it was never much in doubt what would happen.

Mcdu-dotnet lib i use was updated by vradar and now handles PFP7 ( and 3N but i cannot test on this one ) . I will release a version later this evening .

Uninstall then reinstall did the trick. Hopefully the next update goes smoother. Wonderful plugin for Voice Attack and inconceivable to play DCS without it. Thanks!

Hi all. I am inquiring you all if anyone is using a NAS for the DCS dedicated server? I have Ugreen 4800 Plus with 32GB Ram and an SSD that I could use to host the dedicated server. I'd appreciate any insight or information if it possible to use this NAS for a dedicated server.

Good day pilots! In yesterday's update, some may have noticed a slight change in the cockpit with the addition of a WEP master switch as used on some mid and late built F4U-1Ds. Attached is a screenshot from our WIP updated manual regarding its function. And be cautious; engine knock from excessive MAP with or without WEP will cause engine seizures. And there will be a very noticeable knocking sound from it. There is also a big improvement on the engine damage model. Pilots will now have to follow very carefully the limitations in place for the R2800-8W. Time limitations for different settings are realistically reproduced in our model along with temperature constraints. To help you out here is a small summary: Max continuous setting (max temp 232 Celsius) for unlimited time: 2550 RPM and 44’’ MAP for neutral 2550 RPM and 49.5’’ MAP’ for high and low. Military setting (max temp 260 Celsius) for max 30 minutes: 2700 RPM and 54’’ for neutral 2700 RPM and 53’’ for low 2550 RPM and 53’’ for high War emergency power (max temp 260 Celsius) for max 5 minutes: 2700 RPM and 57.5’’ for neutral 2700 RPM and 58.5’’ for low 2550 RPM and 58.5’’ for high Other than that, a lot of graphical bugs were fixed and most importantly, the YE-ZB homing signal sectors have been fixed.

I have had 5 engine stops today, all on approach to the carrier.. It's never happened before. I though of mixture, which I never touch, for simplicity. Here's one that didn't put me in the sea. Should the MP read 30 with the engine stopped? .. F4U carrier U strip 4 prop stop .trk

Monitor resolution? No effect at all.

I'm not sure if I want someone to persuade me to buy one or not to buy one. Cost is a big issue as is reliability (or so it appears on this forum). That said they do appear to be very keen to develop what we need for DCS so that's a big plus. With foveated rendering my 5080 should be OK. I run my QP at pretty high resolution settings so that I offset DLSS ghosting.

nullYou have to choose the right one, see documentation Landing Gear: You must bind "F-23A Gear Up" and "F-23A Gear Down." Default DCS gear controls will not work. • Air Brakes: Use F-23-specific air brake bindings, as default controls are incompatible. Read Documentation

Same here. Also a bunch of modules failed to authorize. Investigating. The game seems to work normally on the 2nd try.

I can't seem to deploy the landing gear, I have bound my keys to use the F-23A systems gear up/gear down commands but it does not seem to work. Is anyone else having the same problem?

So which kind do we have modelled with the M3 F4U and what is the correct mechanization and methodology? Best not guide players to rely on real world manuals by posting excerpts without commentary when it is not clear to what degree and in which specific respects the module correlates with the real world behavior of the real world aircraft.

I use RSBN/PRGM...i dont use ARK navigation...

Seems to have worked fine just now without the error message, so maybe it was just a temporary issue.

Hi RyanR When I select the first target in the TGP, I find the Maverick is off slightly, not by a huge mount but enough. I correct the Maverick and re-bore sight. You'd think that would do it, but I have to do it again on the next target. If I'm lucky. that will do it, but not always, especially if I've been manouvering. If I select the 4first target, make any necessary corrections and then use active pause. all the other targets behave! I use narrow FOV almost exclusively due to being as blind as a bat! I'm that guy who has to turn on labels just to find a target! This is my practice mission. F-16C Boresight.miz BTW ... I might just be imagining it but I think the mavericks align better if I have the laser turned on.

excellent news !

I've solved the problem! Apparently, the issue was having the 'compensate on takeoff' box checked caused the issue. I've unchecked it and things are find now.

Ok so Nate...you get (or seem too) what I'm trying to convey...maybe you can explain it differently to the beta team ?....I just wanted to know if this is how its supposed to work.

I guess we will have to wait. I think what is most frustrating is where we know the CDU is not fully functional, it was at least useable before a couple of updates ago.. I.e not having the screens go blank. I think in most cases, just having it back to the way it was would be good enough for now The other comment I'll make and does echo what Blaine has said. New functions and features are great and shows advancement, but without any supporting documentation or some notes is not especially useful. Like the hover page on the MFD's. Great addition but leaving the customer to figure it out is not great. For someone in the dev team who knows the how, what, when, where and why - it would only take 10-15mins to write enough to explain. I don't think that's too much to be asking for... ?