decipher

these "updates" to TrackIR should really be optional. TrackIR worked flawlessly for many years. my suggestion, just add another option in the settings for everyone to chose between old and new TrackIR behavior...

can confirm this on my system. latest openbeta version i took 2 screenshots within about 3 seconds. before watching into the appr. position of the sun behind the horizon, and while watching in the direction..

reset FBW button (which is clickable, but i was not able to find a shortcut in the settings menu) does actually reset the trim, this was announced by zeus in the last changelog notes.

don't forget that if you are using the openbeta version you are actually supposed to HELP with finding and properly reporting bugs or behavior you think might possibly be bugs, so that the developers (LN in this case) can fix it for the stable releases. now imagine that they fix a lot of bugs, a stable version gets released. but then 2 weeks later.. there is a new openbeta update (and this will soon be a new stable version update) and this new update might mess something up with the aircraft. this is not the fault of the developer, this is part of developing for such an everchanging platform (as DCS world is, with openbeta, stable, openalpha 2.0)... i feel this might triple the headache of developers. to see that the mig21 has a very good and very active update cycle for me is a sign of quality of the developer. they are willing to invest time and manpower in an "older" product. a lot of bugs can be extremely frustrating, especially when you then have to wait for the regular weekly (or sometimes just every two weeks or longer!) updates.. gotta wait and see and fly what you enjoy!

i wonder how much time the real pilots really spend on testing the FM though. i mean you said it yourself, they are busy people and they probably don't have the time to sit down and just fly around for an hour to really test all the different flight situations etc. also it is to be expected that they will "just" fly by the book. when they fly the real thing, they will not start to think "hey i wonder how this helicopter behaves if i turn off SAS and press the rudder full left in a 5 meter high hover!". they will fly within the regulations, so even if they say the poly-gazelle "feels like the real thing", this might only be for the actual "normal" operations, not extreme situations and weird control inputs, that are not to be expected within the regulations. the thing is, even 10 year old FSX airplanes and helicopters had real pilots "test" them and say "hey this feels like the real thing, you can fly it by the flight manual and numbers"... but they were just using the basic fsx FM with just some tuning to fit the model. i don't know how much math and physics the coder has to actually know to implement a helicopter FM within DCS and how much of the physics and "world integration" (wind, gravity, aerodynamics etc) are set variables and routines from the DCS code, but it should also be considered, that the coder might just have some physics of helicopter flight just wrong, that only come to light in extreme situations (that a real pilot would avoid at all costs in the first place and probably never test without being specifically asked)

affects all modules, reported and on the list http://forums.eagle.ru/showthread.php?t=169144

tested your observation with a slightly bigger AI aircraft :)

+1, i am using no texture mods or anything.

did a quick test, with openbeta 1.5.4, no mods installed, started all three missions. they work for me. each mission comes with a selector after starting for "hot" or "cold" startup. i chose each option in each mission, all resulted in proper cockpit. i would suggest doing a repair on your installation maybe?

i just tried this with openbeta 1.5.4 and all seats work for me, did you check your shortcut assignments etc?

some more screenshots to demonstrate, the sun glare will actually disappear through a propeller, and then re-appear when behind solid metal! pictures were taken within 2-3 seconds.

heads up for everyone who is interested. it seems like they added this to the latest 1.5.4 openbeta udpate! i now have an option for "flaps up" "flaps down" that when assigned to a three way switch, toggle it perfectly like with A10C. up, middle, down. very nice little addition. thanks ED for adding this (quick note: i had to clear my old flaps button assignments and restart DCS, then i was able to re-assign the new flap toggle shortcuts - this way you can keep all your other shortcut assignments...)

latest open beta update, no mods. this is an initial quick report to see if others have the same problem and can re-create this. tried with various modules, it is not related to different types of aircraft. the sun glare / flare is rendered through everything.

haha sorry guys, now it looks like i spammed the answers, but i just answered to different threads about trackIR problems in the different forums [for mirage, mig21, gazelle, etc] , to help people find the fix. now it all got moved together to this thread :)

fix from skatezilla, might have been buried in the postings: http://forums.eagle.ru/showthread.php?p=2822647#post2822647 works perfect for me

oh yeah it was kind of messy. and several things not working anymore, BUT skatezilla worked hard with the testing and they found a workaround already that fixed the issues completely for me... just in case, it was easy to miss: http://forums.eagle.ru/showthread.php?p=2822647#post2822647

trackIR fix from skatezilla to fix all issues related to messed up trackIR: http://forums.eagle.ru/showthread.php?p=2822647#post2822647

skatezilla presented a workaround that fixed all TrackIR issues for me and others: http://forums.eagle.ru/showthread.php?p=2822647#post2822647

can confirm, fixed all trackIR issues for me!

thankyouverymuch! this fixed the issues for me. thanks for figuring this out and finding a workaround, much appreciated!

thanks for explaining and i understand, but i was not meaning razbam testing or you specifically, sorry if it sounded that way! :) from reading the mirage forum i know you are really working hard and always very helpful and communicative with updates etc. i was probably thinking more of general ED testers, those people who play with the whole update before it gets put on open-beta.

these issues are all over the place, trackIR problems, messed up axis assignments, slanted / tilted horizontal views or unresponsive behavior, black screen after trying to save options. changing the options.lua to disable VR doesnt help. lots of people reporting these problems, crazy that those could have been missed in interntal testing...

updated to openbeta 1.5.4 and now having problems with the trackIR viewing system (like many others reported on the bug forums) so instead of driving myself insane over this i gonna have to take a break from open conflict (and dcsworld) and head over to the skies of ww1 and 2 for a while . don't update too much in the meantime, mirknir! too bad there is no "OPEN CONFLICT" server in rise of flight :D

interesting. for me the mig21 was the only module that worked properly with trackir (my setup: 1 display screen, trackir5, no VR). nothing seemed to have changed, my trackIR settings were working normal like before the update, but all other modules i tried, they now have messed up trackir movement (seems like some axis are mixed up, yaw and pitch are not set properly anymore etc ).

to me it looks like some axis assignments of the Track-IR section are messed up after update. i had my trackIR set up properly for all my modules, now for example in the UH-1H the axis for "horizontal movement" is blank, it was on trackir_yaw before.some axes might even be switched around (like tilting axis on vertical axis or other weird things) edit: when re-assigning the axis for yaw and pitch (which were blank after update) i noticed that the yaw rotation is not horizontal anymore. meaning: when you look left completely horizontal, the view tilts to the side.... i guess they adjusted something for the VR stuff...