Shaman

That could be also a Special setting to change its default state.

Nav lights and anti-col light are still very weak in daylight, is it a DCS engine issue? You'd expect you can spot these at long ranges.

It would be great if there was a highlight like during training missions what you are expected to check switch next, when Jester calls it.

I can't get rudder deadzone to work on my end. Could it be related? No matter the value of rudder axis deadzone I apply, I don't get any, there is nil change while in cockpit with controls overlay view.

bump, bug is still present in Feb 2025... I just turned it off completely.

It is definitely a bug. Even if you want to take control at last mile, you basically run out of trim range... there's no way to pull up after ACLS is disabled at last mile and you wish to save the airplane.

I have to admit that since Sep 2024 when I got FBB (VPForce base) I am having issues with autopilot altitude hold (not every time though) and ACLS too (pretty much all the time, despite being very careful with glideslope capture and in perfect trim).

Since this thread has been ressurected. I have tried it with FFB stick (VPForce). It is not working well if FFB Trim Actuator special function is set to on. Even if FFB Trim Actuator special function is set to off, ACLS is all over the place with ATC on. Tested it again and again being perfectly trimmed on glidepath and according to procedures. It might be FFB implentation that throws its logic off. Something for Heatblur to test. I think it ACLS is quite useless with proper FFB gear and will just get you killed.

I have been flying ED sim since Su-27 Flanker 1.0 demo released by SSI in 1995. Every single iteration of their product. This outcry for them trying their chance with F-35A is just insane. When first Su-27 sim was released aircraft was like a decade in service. When Jane's released their F-15E and F/A-18E, Strike Eagle was like decade in service, the Super Hornet entered service like a year prior. Now when ED releases their F-35A (likely in 2-3 years time), this aircraft will be in service for over a decade. There will be enough information to make it a cool consumer market level study simulation game out of it. If you are hating this or that module announcement for any reason, it only tells what kind of person you are. I personally keep waiting for full fidelity Su-27S, but I am still happy will receive MiG-29A. Some of you are so difficult to satisfy.

I have just found this thread. I wonder whether within a year time module developers have already implemented this optimization to their own set of liveries or they have not?

Yea, would be nice to have your AI wingman switch to F2F Datalink on request.

So what did you do wrong settings wise, so other users can find their answer?

I have just gotten to fly DCS in Quest 3... I think I know what the problem is. I think the reason is we tend to lean back on our seats (I have ACES II replica) due to seat construction, also the weight of VR headset makes us raise our chin compared to where our head would be without them. The HMD is perfectly centered on screen and this is why ED devs can't replicate this issue. HMD vertical adjustment should be a special option for every module, not only Ka-50 2 and Ka-50 III.

Switching to 500Hz in Amoury Cate for my ROG Spartha has resolved the stutters. How annoying! You only get few hours to play a week and everytime you return you must troubleshoot something after DCS update.

I am having a problem with checklist stuck after "harness" step - my pilot positively confirms it and it just doesn't progress further. No idea what is going on.

Inside Special F-4 options, increase FFB gain to at least 200% Roll. I also use 150% for pitch now. VPforce Rhino - with curved extension 15cm and TM Warthog stick on top of it. The top two FFB options are off in my profile. Stick deflection limited off Stick force blending off

Encountered similar problem on VPForce Rhino FFB stick.

Having similar problem on VPForce Rhino FFB stick.

No matter how many GBU's I throw at static structure named WC it won't even smoke

Okay, I think the reason was 5m/s cross wind about 90 deg to the flight deck in ME I have not noticed. Silly me.

HI, I am trying to do ACLS CASE III traps, but it is attempting to kill me. I use default load of weather called Summer & Rain. No idea what is going on, it attempts to trap way way far to the left and way way far too short.

Adding my latest tweaks for proper neck mod to work with latest modules for TrackIR users. The biggest noticeable difference is HUD image when you try to turn your head like IRL and when checking six or looking down. It is more immersive that having camera fixed on a pole. My SnapViews also incorporate tweaks to center position incl. It also sets FOV to 90 degree as default and for zoom view (fov) axis (min 30, max 150 deg) for a/c I fly. My eyepoint vs neck lenght is 10cm x 10cm default to reduce effect by PeterP. I have tested with my one eye closed in the pit in RL and it is more acceptable imho. In the end it is all matter of preference so edit files as you require. Imho: eypoint offset from neck should be 5cm (conservative) or 10cm (good default), 16cm causes unrealistic rapid viewpoint travel when you turn your head down. shoulder good default is .15 as it does not cause such excessive camera movement on "shoulder rails" as you turn head past 3-9 o'clock. .25 was good for view hat users but with TrackIR you have 6DOF to control that. AH-64 boresight position readied as default. Also fixed shoulder for F-14 pilot seat (back seat was ok), and both F-14 seats use the default 5cm eyepoint offset from neck - increase it to 10cm if you wish. Note: this does not work entirely when joining some servers. Shoulder value is basically a scripted distance that offsets camera on left or right rail when you check six. Remember this is to increase immersion for TrackIR overs, these servers might force different eye point position at start and shoulder. Remember to check first post by PeterP to understand what Eyepoint values does. Mod is no good if you are using hats or eye trackers, and it is totally not for VR (which uses own hardware and DCS settings for proper head and eye position tracking). SnapViews.lua Server.lua

Hi eFirehawk, I know what you are trying to achieve. I also use immersive real neck view tweak, please place my files into \Saved Games\****\Config\View This will set you up for most popular modules including Strike Eagle. Difference is significant. Notice that certain popular multiplayer servers lock the use of custom server.lua and things go weird from there if you have tweaked default position in snapview.lua to accomodate changes in server.lua. Server.lua SnapViews.lua

Precisely, it must be the Server.lua file with custom view settings that likely are saved into the mission file that server is hosting and it enforces it on the other users and in effect messing with my own custom setting to my monitor setup and cascading down also on default snapview settings. I just refuse now flying these servers. There is nothing else I can see I can do. There is no way to see through lobby if server is enforcing own custom server.lua in mission file.

I am using customer server.lua in user folders to adjust neck height, eye point and shoulder width to resemble real neck as it improves my immersion with TrackIR. This also requires I adjust by tiny bit default camera position in cockpit for modules I own. However every time I join multiplayer server (not of my own) all goes wrong, some camera view settings modify to a point my HUD is cropped significantly, when I turn to check 5-6 o clock I am in that weird position etc. There is nothing in the MP lobby that describes to me server is using locked customer server.lua view settings of their own? Is there any way to resolve this issue or is it just the way it is? Is it because by some mission developers their own server.lua view settings are saved into the mission file and then forced on connecting clients? I.e. I join Grayflag server - I run my settings; I join Growling server or Blue Flag I run someone else settings incompatible with mine... Server.lua SnapViews.lua