stelr

My squadmates and I see the exact same. In level flight, at 2700 RPM (max), when I push the throttle past the wire gate (detent), the animation is correct but there is no change to manifold pressure at all. I see others posting that they get an additional 10 kts doing this, but not so for anyone I have talked to or flown with. Am I missing something, or doing something wrong? And to clarify, this in no way refers to the bug in the RPM lever that can provide ~3200 RPM by using the mouse to push the lever down further. That is a separate issue. it just seems, in my experience, that water injection/WEP is not yet implemented.

Do you mean the "throttle"(MP) or are you talking about the "propeller governor handle (RPM)?" I read where after moving the prop governor handle to its full throw (down), you can use the mouse to move it down more to achieve ~3200 RPM and >70 in of mercury manifold pressure. Engine will overheat pretty quickly, so need to watch carb temps. Should it even be able to achieve these settings, or is this a bug? In either case, without doing the above, I really can't achieve speeds in excess of 250 kts in level flight. Same with others I fly with. That's with all cooling close, <50% fuel, and trimmed out for hands off flight. It seems like there is some invisible drag, or hidden extra weight. This also negatively impacts roll rate.

Not to be picky, but unless I wasn't watching close enough, I didn't see any parachutes or static lines attached to the cargo loads on the heavy drops as they are sitting on their pallets (also lack all the layers of honeycomb that would be visible on the bottom and top, just under the chutes). Riggers are gonna get their collective butts chewed for trashing all those supplies.

Sorry, but latecomer to this issue. Pimax Crystal here, using a 3090, so QuadViews is essential. I have the same issue and cannot fly until HotFix from DCS. PLEEEESE prioritize this issue ED!

Just downloaded the update and had a similar message from BitDefender but with a different file. Mine said..."The file C:\Program Files\Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\Mirage-F1\bin\MirageF1Core.dll is infected with Gen:Variant.Tedy.380857 and was moved to quarantine. It is recommended that you run a System Scan to make sure your system is clean." This appears to be a Mod File (CoreMods), but I do not use mods and do not own the MirageF1.

Thanks. I'll give it a shot on the next mission.

Thanks, but I cannot access any command menus once my plane lifts off. I have the "\" button programmed for menu but it only works when I am on the ground.

Cannot land on missions after mission #5. So far on missions 6 & 7 my wingman always...always blows up on my very close 4 o'clock on short final, destroying my aircraft along with his. There is no way to get rid of him short of shooting him down myself. Seems he thinks this is a Blue Angels demo...and he fails to avoid colliding with his lead.

Was wondering if anyone here has used, or is using the PIMAX 8KX in DCS. Looking for feedback on the wide FOV available in the PIMAX headset vs the more limited FOV available in the G2 and how important the FOV is to SA and immersion. I understand there is a trade-off in visual clarity, with the G2 being sharper. That said, how much of a trade-off, and if so, is it worth it not considering the differences in cost. Please reply if you have actual experience with one, or preferably both these systems. Appreciate any assistance. v/r Stel

Same issue on P-51 module using Normandy map.

Exact same issues here with sound w/P-51 module. Tried F-18 module, but sound issue did not occur. Will have to test more, but anyone else having this issue, and is it limited to P-51 module??

Thanks Rangi! That seemed to do the trick. Mirrors working again. :)

After changing back from DCS World v1.5 Early Access to DCS World v1.5, my rear view mirror in the P-51D no longer works. The mirror is there, but instead of a rear view, there is only a green and brown pattern (similar to a camouflage pattern). It seems the textures are not displaying properly. The mirrors worked before in earlier release versions and in v1.5 Early Access; so not sure what is wrong. I have rebooted several times, so that isn't the issue. Not a memory issue either as I have 16Gig of RAM and a 4Gig graphics card. The HD is a 1TB SSD. Any ideas on how to fix? Tks in advance for any assistance.

I have begun having the exact same issues after the last update. Never happened before. I have tried the above recommended solutions with no result. I couldn't find an "Auto Time Zone" drop down box in my profile or Personal Section, so maybe there isn't one on the new GUI for the website. Don't know. I believe my problem may be an issue with PW. I didn't change it, but suddenly, my LOGIN was no longer accepted on the website, so I had to click the "Can't remember PW" and have them send me a new one so I could change it. After that, my new PW works fine to log me in to the webpage and FORUMs; however, even when I made sure the new PW was correctly entered in the simulation (when prompted for entering Multiplayer), it comes back with cannot connect to Main Server. I then tried to enter "Module Manager" and it came back with incorrect PW! I then clicked on "Register" to ensure my user name and PW were registered correctly and it said I was logged in and registered! But...the game will still not LOG me in to join Multiplayer???? Anyone with any other ideas??

Thanks you Buzzles! That was it. I had named the folder "F-86f" as instructed in the "Read Me" in the skin folder I downloaded. Making the correction you suggest made all the skins I downloaded now available. Very much appreciate the kind assist. V/R Stel

I tried it as well, loading several skin folders I downloaded, but the drop down box still show no skins available. Seems there is a broke link between the Liveries folder and the mission editor. :helpsmilie:

You may be right Skatezilla, and probably are, but it just makes sense for developers to contact other developers on conflict issues, as well as having the customers do same. When it comes to programming I'm like a pig looking at a watch. BD could easily blow smoke up my posterior and I wouldn't be the wiser. OTOH, a developer could easily explain the issue and maybe resolve it at the lowest level. Good for business for both. Just saying... v/r Stel

They finally sent me a copy of the new updater file and I just dropped it in the bin folder (bypassing the requirement to "self download" by the old updater) and all seems to be working fine now. The real test will be when the next update to 1.2.8 comes out to see if it downloads automatically w/o a conflict. I appreciate their help. Hope this BD conflict issue gets resolved before the WWII initiative comes out. It's a long way off. maybe I'll find a new AV by then.

I didn't remove it at all. I just got a copy of the "DCS_updater.exe" and placed it into the "bin" file. If anyone here has a copy of the 2.4.1 updater they can post here for download, it would be appreciated. It's worth a try.

I have the same exact problem Rico. Had it when updating from 1.2.7 as well. I finally got it updated, but had to get a copy of the updater itself sent to me and put it in the bin file. I opened a Trouble Ticket with DCS, but they response was very unhelpful and they didn't try to help at all so far. They just say that the problem is with my AV (BitDefender) and that I should dump BD and then all will be well. But...I want to keep BD, and not keep switching AVs every time DCS decides to change their code. I would expect they would contact BD and try to resolve any conflict, but they don't seem interested in helping the customer. Exactly what could I tell BD to convince them that something is wrong with their code? It works with all other sims...and worked with DCS before THEY changed something. Unfortunately, DCS seems tone deaf on this issue. I hope they become more cooperative and less adversarial in their approach to issues. With the current attitude, nothing will be resolved.

OK...having exactly the same issue (including use of Bit Defender AV...turned off). The last few posts seem to be high fiving that a solution was at hand, but not being a computer experten, am having problems understanding what I need to do to get this update. Is there a simple answer...or do we "few isolated cases" just have to move on? :helpsmilie: v/r Stel

It appears that the latest version of TeamSpeak 3, just recently released has fixed this problem in both DCS and ROF for me. v/r BSS Stel

PROBLEM RESOLVED! From others I was flying with, it appears that many of the "actions" listed in the Controls were missing from my game, including the three critical ones that allow the Mouse "X", "Y" and "Z" axis to be mapped to the external views. One of my friends emailed me his "Mouse.lua" file which I used to replace my file and that fixed the problem. v/r BSS Stel

It happens all the time. It has never worked. It must be a mapping problem is all I can figure. I can't find the command that allows the mouse to control the camera.

I can get to external view of the aircraft by hitting F2, but the camera remains locked in one position. I'd like the mouse to move the camera position around but I can find no command to make it do so. Can anyone tell me how this is done? :helpsmilie: v/r Stel