Irk26

Same issue. Does not work... at all. It used to. Force Trim switch is on. Tried with Misc > Force Feedback both on and off and completely restarted the sim between changes. Pressing the Pilot Trimmer button just makes the button on the cyclic depress. That's it. It otherwise does nothing. Has this even been acknowledged as a bug yet? Seriously, please fix. It can't be that difficult... 2.7.3.8494 Edit: Nevermind. Found the problem, in case anybody else lands here with this issue. Not only do you have to deselect Force Feedback, you also have to know to go into the "Special" menu, select UH-1H down the left side, then set your Trimmer Mode. In my case, it had to be set to "Central Position Tirmmer Mode." Also make sure "Autopilot Availability" is checked.

Same here... on multiple aircraft, default included. Parts missing from the aircraft. Edit: I think this is an acknowledged bug.

Same here. Clean install today.

Crashing on exit from VR, for me. Fxo and metashaders were deleted.

So is there a solution to this yet? I can't even see the runway until I'm practically on top of it because everything is blooming so bad? Like everything's just a wall of white. It's really not usable the way it is. I'm on 2.5.6.55363

Same issue. With Stennis. My flight is temporarily delayed to start. Please wait.

Happens to me, too.

It's on the console, at the base of the throttle handle, on the left side of it, and slightly behind it. I disagree with whoever said it's real obvious in VR. It wasn't to me. It's a tiny black handle, on a black panel, hidden behind the large black throttle handle. I was looking right at it, multiple times, and never saw it. It's practically invisible. If you move your cursor around the base of the throttle you'll see it turn into the green up/down arrows at some point. That's the parking brake... even though you can't really see it.

+1

+1

Is there a reason we can't have fog when it's dark? 21:00 (daylight) full fog 21:15 (dusk) fog greatly diminished 21:30 (dark) no fog Fog appears to only work in daylight. Desktop or VR Stable 2.5.3.23225

Yep, that's where it went. Probably the last place I'd have thought to look for it. Thanks :)

As the title says, I have no Start Time option in Mission Editor - Briefing. Anybody know if it's broken right now, or am I missing something? I haven't used it in a while but I do remember seeing it there before... (Stable 2.5.3.23225)

Yeah, I REALLY wish they'd give us a way to decouple the mouse cursor from head tracking. It's so difficult, and annoying, to use. It's easy to keep the mouse still but not nearly as easy to keep your head still while you're trying to line up and click on something. And it happens frequently where I want to position the cursor on something to be able to click a few seconds from now, while looking elsewhere (simple example: cursor on BALT while watching altimeter to click at a certain altitude... which of course you can't do).

Yeah, you were right. That fixed it. Thanks. I was avoiding updates because mods that don't live in saved games, and I didn't see anything in the changelogs that affected me. Guess I'll have to rethink my stance on that one :)

I'm a complete n00b to this but there are zero servers listed when I go to multiplayer. From what I've read and watched on youtube, the list should just populate, no? Is there some setup somewhere that I'm missing? I'm on stable 2.5.2.20601 Edit: no firewall or AV

Way cool . +1

Just shut up and take my money, Heatblur :D

More update: since .20601 the issue has crept into NTTR as well now. Anything over 1.7 is pretty much guaranteed not to work... at least for me...

FOUND IT! If the pixel density is about 1.7 or greater, PG will not run in VR. 1.6 or below, works fine. 1.7 or above, stops working. And I get those exact "SecurityControl" lines in the log. In brief, I just did what you said, Ian, and followed it fully through: Renamed the DCS folder. The newly created one worked. Started transferring stuff from the old to the new. Narrowed the problem down to Config\options.lua. Then diff'd the working and non-working options files, swapping one line in at a time from bad to good until it broke. That turned out to be the "pixel_density" line which was set to 1.8 in the old config. Then I just dropped the value one notch at a time until it started working again. That turned out to be 1.6 It's actually a little wonky in that those numbers are not hard and fast. 1.6 or under seems to work every time. 1.7, it'll work most of the time. 1.8, will pretty much never work... just once in a blue moon. Anyway, however the numbers work, the problem does appear to be tied to pixel density.

Hey thanks for the reply, Ian. For sure antivirus is not the issue because when I had the original problem, I had no anti-virus installed at all. I don't know if it makes any difference to what you're suggesting but I haven't flown a single mission so far. I've just been flying in Instant Action or Training. If what you're suggesting to try is still relevant however, I need a little more detail: -What folder specifically do I rename in DCS World\MissionEditor? There are multiple folders with multiple sub-levels below them and I don't see any one that refers to Persian Gulf in any way. -Or same question for Saved Games. I don't see anything in the MissionEditor folder there that looks like it applies. All I have in there is a few files and one folder named Weather. I've posted the current log but it looks pretty much identical to the one I posted at the top. According to tech support the problem is this: 2018-07-28 00:46:12.104 ERROR SECURITYCONTROL: failed to load mods/terrains/persiangulf/terrain.cfg.lua.dll.crypt 2018-07-28 00:46:12.104 ERROR SECURITYCONTROL: Failed to load mods/terrains/persiangulf/terrain.cfg.lua.dll 2018-07-28 00:46:12.104 ERROR DCS: Can't load terrain from ./Mods/terrains/PersianGulf\terrain.cfg.lua They say something is interfering with crypt but if the problem was on my side, I'd would expect other DLC to have similar issues. The fact that this is confined to PG only in VR makes me think the issue is with PG. Anyway, I think tech support has given up because they can't reproduce it and they say no other users have the problem. I let them know about the similar issue Chopper A-10 was having but I still haven't heard anything from them unfortunately. dcs.log.txt

Well, crap, DCS crashed tonight (first time it's ever done that) and now PG DOES NOT work again. And I wasn't even in PG when the crash happened. I was in NTTR with the Hornet. After a reboot, I looked through the crash logs and saw mention of PG -which I wasn't even using at the time- but it prompted me to check it. Sure enough, not working in VR again. *sigh*

Yeah, this. When 'Use Mouse' is enabled, the blue VR cursor should not move around with headset movement. Please, just give me the option to turn off the HMD steering of the cursor if I'm using mouse. It's difficult and sometimes frustrating to use when the two are coupled.

Yeah, I saw your post, Chopper. I debated whether to jump in there or not. Yours was very similar but not exactly the same. Glad you got yours working too! Weird problem,man. Even reinstalling my DCS and PG didn't work. I've had a ticket in with ED for a while so I don't know if they actually found and fixed something or it's just incidental that .20143 fixed the problem. I haven't heard anything back yet. Anyway, at least we're both back in business :D

Update 2.5.2.20143 fixed the problem somehow :)