smallberries

I suspect engine performance degradation too, I don't think it's quite modelled right atm and might be a randomish gremlin.

Yeah, you're due for a complete. That being said, I did my overhaul in bits, and I got my GPU months before I managed to get the CPU/Mobo. If you can only do 1 thing now, that would be the way to go.

Samsung (Magician?) has a tool that will move your Windows install for you. I used it when I went from HDD to my first SSD, and it worked just fine.

I agree the granularity of the push button trimming system is too coarse for fine adjustments, and ends up being a pita. Hopefully at some point ED can implement a finer controllability. Perhaps one with an accelerating scale if the button is held.

Awesome to see both VKB and VPC getting busy with giving us new toys. One thought, maybe some day down the line, but as someone who will likely be swapping from airplane/throttle games to space sims and dual sticking it, and as long as the grips are modular, it would be awesome if there was a way to remove the throttle grips and swap in a LH stick :-) I can dream, can't I? (with twist)

I did the sanding thing and tried spring modding a bit before getting a VKB base. Unfortunately, I don't think VKB is selling the standalone base anymore, fwiw. The sanding definitely helped, but in spite of all my care I did cut the insulation on one of the wires putting it back together. Be warned. But, yes, the VKB base is smoother still. An extension might help too, although the weight of the grip and leverage of the extension may mean you end up wanting more stiffness of the springs if you want to keep any centering tendency (I'm looking at you, helo trimming).

I had a spate of crashes when practicing helo landing on the boats, specifically the dest with the helo pad at the back. Not the smaller dest with the pad at the very back, but the one with the helo pad a level up. Since I stopped trying that out I don't think I have had any.

I don't think the Harrier is supposed to be landed conventionally?

Then I'm stumped. Hopefully someone else has an idea. Good luck!

I would check first to see if there is sunlight playing havoc with you. There is a way to get the application to show where light is striking it from, but an easier way is to drape your area so little to no light can get in and see if your TrackIR starts working correctly. Even indirect sunlight, bouncing off a wall, can trick the camera. Anyways, for an assymetrical and erratic behaviour, that's my best guess. The only other thought I have is that something is occluding the view, meaning your camera can't see your clip when you turn your head a certain way because your head or something else gets in the way. Your camera should be offset to the side of your monitor your clip is on, so it gets a good view even when you turn your head.

Well, that about covers it.

This can happen when the in-game throttle isn't correctly matched with your throttle at the beginning. I have had it too, where my throttle idle is calibrated with throttle off in-game. Probably because the my throttle was in the idle position when I fired up the module.

It's not just whether your CPU will be enough for DCS, because it will. The extra cores are nice if you have other things running, though, like a chat program or your browser open, etc. If that doesn't concern you, then by all means save your money. Down the road developers are going to focus more and more on using the extra cores, though.

Thank you!

I think I saw this question asked in another thread but saw no answer to it....while I have no problem snapping a fresh Mav to the DMT, if I slew a Mav there doesn't seem to be any way to cage the Mav again so that I can subsequently uncage it to the DMT target, and I have to manually walk it onto the target, unless I completely undesignate the DMT target. Is there a way to boresight, cage, or otherwise snap a slewed seeker head back to a designated DMT target without undesignating the DMT first?

I'm not sure I understand why you would want to go beyond a single 1080ti? I can max all settings and my 1080ti doesn't go past 50% usage...frames are quite good, frames are around 60 actually...even if DCS could utilize SLI, if a card isn't running near full usage, are you going to get more fps?

Basically, if the analogue mini-stick is better than the crap on the TMWH, I might have to switch :) Although thumb would be weird...

Dear Santa,

I can't say it with 100% confidence, but I have been paying a lot of attention to JPT to try to learn to VTOL/land with a load, properly, and in some of my missions that involve many attempts and just re-selecting my role and trying again....it seems the OT state can remain from an old plane when you spawn a new one. A fresh plane should start off saying OT 4 secs on the ENG page in the MFD, and I have noticed a fresh plane saying 43 secs (a sign of overheating, although I don't really know what it means yet), and ofc the OT warning light is on, immediately after spooling up normally. This is immediately following a normal cold start, so I think the bug is that the OT state is persistent within a mission between spawns, or can be perhaps, based on your DCS install. I have also been getting a bug where trying to get the ground crew to reduce my fuel has resulted in fuel being added, or the ground crew claiming to change the loadout (without any changes being requested to weapons) instead, and I've had to request this several times before it happens properly, but none of my friends have reported it, so maybe it's quirky and it's just some of us getting some odd bugs (British humour)?

Or, just do as I did, and rebind everything! Such good practice! :doh:

No mods installed, it has persisted through a few patches, and I did a repair once as well. Just trying the scale GUI option now.... AAAAnd fixed. So easy. Wish I had thought of that before, thank you everyone!! In fact, everything looks nicer, menus etc....so fwiw I have a 2560x1440 monitor, and idk if that's material, but definitely scale GUI is not a good idea for me.

Last try, and an interesting observation. The map layers work fine in the mission editor. It's only in-cockpit that this bug appears.

No joy?

What Ocelotunit means is it's under the command AG Target Undesignate / NWS / FOV Toggle....right near the top which makes it easy to miss when you're scanning for Nose Wheel Steering or NWS :)

Thanks for the answer. I live in the country and can't always count on my internet. Of course, I can't always count on the power, either...