jjohnson241

Found the answer: The USE FF option was on in all three of my DCS installs. I know I had it off but I have no idea when it crept back to "on". Anyhow, clear that option and all is well with the Trim. :)

Thanks. Any thoughts on what to do when you change position of the cyclic and want to trim that position? Do you reset trim first before moving to the new trim position?

Hi, Anyone help with the correct procedure to apply the magnetic brake? I've been having problems applying and re-applying the magnetic brake. What is the process to 1) apply the brake initially, and 2) reapply the brake after changing the position of the cyclic? Do you have to hit the reset trimmer button, either initially and/or before adjusting the cyclic and reapplying the brake? Thanks

Hi, This thread (https://forums.eagle.ru/showthread.php?t=176981) should be moved here. Any news on the tests that were scheduled for last week? Thanks

If you ran the update for DCS 2, you should have a working Gazelle. I've been flying her since the update and other than the trim being borked, the module flies.

The bug was reported to be in DCS 1.5.5. I wanted Poly to understand that the bug was also in DCS 2.0. Also, this bug is serious IMO and in the opinion of others affected. The bug was reported 10 days ago and no word yet other than it's on this weeks test schedule, I assume to verify that the bug is "real". Finally, 10 days is more than a reasonable length of time in terms of waiting to hear from the developer . So, guilty for "spreading it around". ;)

trim problem The Trim problem described here: https://forums.eagle.ru/showthread.php?t=177452 is affecting the Gazelle in the DCS 2 -NTTR also. Anyone else having this problem?

Now that the Gazelle has been restored in DCS 2 NTTR, the Trim problem is now affecting DCS 1.5.5 and DCS 2.0.4 - NTTR. Any news from the scheduled test?

Trim Reversed Description: Trim action is reversed, i.e., Trim Nose Up command results in nose down trim, Trim Nose Down command results in nose up trim, Left Wing Down command results in right wing down, etc. Single Player Non Steam To recreate: Start, Fly and apply trim Controllers: HOTAS Warthog using POV Hat on Joystick for trim input. O/S: Windows 10 32GB RAM GTX 1070 4GB No Mods used to recreate Note: Reported in Bugs thread by other players as early as 11/13/16

Same Issue here with Thrustmaster HOTAS Warthog and VKB Rudder Pedals, Single Player, DCS 1.5.5 Public release and BETA Release. I7-6700K, 32GB RAM, GTX 1070 4GB. Pitch and Roll trim axes are reversed. I also noticed that after I applied the magnetic brake trim, then released the trim, I could not apply Magnetic Trim again. I don't think that's correct. Magnetic Trim should be enabled and released as many times as desired. I noticed the trim problem was initially reported over 9 days ago and Trouble Tickets were issued. What's the status, Please?

Well I've "stayed tuned" but have seen no update. Can Poly provide a status please?

I have the same problem with the LED based Pro Clip and for that reason I went back to the visor clip. I have no problems using the visor clip. I'm sure that if you use the TIR GUI, you could adjust the range when the LED clip is used. I just never tried it.

What Option are you using for the Terrain shadows? I flew with "Default" and I see large groups of trees in the Free Flight - SU25T mission. Not sure if those are "forests" but it looks like in your screen shots that you have groups of trees and also areas where there should be trees but no trees are there. Hard to tell without side by side screen shots of the same area.

Thank you sir.

Hi, Happening in all three copies, M-2000C Instant Action mission (Takeoff), exit mission then hit "Refly" from briefing screen, game crashes. As far as I can tell, only happening with M-2000C. Mods or no. I've attached my logs from the OpenBETA copy. As I said, it's happening on all three copies. I deleted the M-2000C from Configuration - Saved Games with no impact on the problem. Problem started I believe with last weeks update to Stable and OpenBETA and moved to Alpha copy today. Logs.rar

+1. Only does it in 2.0.3. 1.5.4. is OK. I had to use the Task Manager to end the DCS Task in 2.0.3. Instant Action mission to different mission load times are OK. The problem seems to be limited to "Fly Again" (same mission), at least that's what I'm seeing. A potential work-around is to completely exit the mission to the main menu and then select via the mission menu rather than "Fly Again".

Great, glad you worked it out. I'm not familiar with Mudspikes "Vivid Colors" mod. Is that a P-51D specific mod? EDIT: Never mind Chief, I found Mudspike's mod in the user files section.

Have not spent too much time with the plane yet but I noticed the sensitivity of the NWS. Far too sensitive.

Chief, The path was the problem in my installs. With Eagle dynamics/DCS World in the path I was not getting the mod installed. Without it and starting with Mods in the folder structure, I got the mod installed no problem. The other thing you may check is that JSGME is pointed at the _Mods folder as the location of the mods. That might have been the problem with the Eagle Dynamics in the path. I was not getting the mod installed. Don't know what else to tell you. Again, the path was my problem.

Skull, I have your Mod installed in both the Stable and OpenBeta release of 1.5.4. No problem. But, I modified your JSGME file structure to begin with the Mods folder, not the Eagle Dynamics/DCS World path. I had to do that to install the mod in the correct path. I believe that is Chief's problem. Restructure the path in the JSGME to Mods/Aircraft/... not Eagle Dynamics/DCS World/Mods.... and you'll be OK.

The F-86 has the same type of "hold and go" system. Took me awhile to get used to that also.

I too had no TIR movement in the aircraft listed above (I don't own the Gazelle) in both the BETA and Stable releases. I had to delete the aircraft from Config/Input in Saved Games then reassign the controller options. I don't know what's causing the TIR problem but I had the same thing happen after the last update to 1.5.4. Is the fact that these aircraft have not been updated to the new TIR setup causing this problem?

Despite several searches I can't find the 1.5.4 TrackIR Behavior thread. Can someone provide a link to that thread? Thanks Edit: Please disregard, I found the thread.

+1

I have an A-10C profile in my TIR titles and it activates a hen I fly the A -10C. I adjusted the view center in that profile and it worked. The Profile may have been a residual from the old stand-alone A-10C but I know I didn't create the profile. It works and that's all that matters. Hi