PeterP

Attached you will find the first beta of Reworked Cockpit Views with proper Neck plus 6DOF for Mig-29 , Su-33 and Su-25T for DCS World 1.2.4 BETA All cockpit views (for all flyable modules/planes) have the 10cm up and 16cm forward movement of the eye-point to simulate a neck. Some of the "limits_6DOF" values still need some tweaking - but its fairly well done (I hope) , I just didn't spend a lot of time if I'm able to move the virtual head inside the panels or through the closed canopy. (...wife started to be a little upset because I spend the Friday evening reloading DCS again and again... - and it just makes no sense to anyone outside watching me quitting the simulation just 3 seconds after starting - retyping something in the editor - and starting over again... ;) - so I quitted after I thought that I roughly nailed it down - next editing time is Sunday...) As I said before : It's still a beta and maybe needs still some tweaking. And when you followed this tread and/or only the last 10 posts you will know why. So if you don't like surprises - just wait until I have nailed everything down and and it isn't 'beta' any more. ...and I added a proper readme and more detailed info. If you try , you should really have a look how to customize your own default cockpit view when using this files. Here is a "HowTo" >>> http://en.wiki.eagle.ru/wiki/Snap_views I already enabled the snap-views saving in the attached default View.lua - so no need for you to do the edit - just posting the link for completeness. and here is a list of the needed key-commands. (Yes - I know how hard it is for some of you to look it up your own in the options ...;)) Disable your Track-IR/Head-tracker while doing it ! "Num/ - RCtrl - RShift" Cockpit Camera Move Back "Num5 - RCtrl - RShift" Cockpit Camera Move Center "Num2 - RCtrl - RShift" Cockpit Camera Move Down "Num* - RCtrl - RShift" Cockpit Camera Move Forward "Num8 - RCtrl - RShift" Cockpit Camera Move Up "Num/" FOV- aka Zoom-in "Num*" FOV+ aka Zoom-out "NumEnter" Default FOV aka Zoom "RCtrl+Num0" Save current Cockpit view as default for this vehicle How to install: And once again - safety first : Always make a Backup before you change your files and use a proper editor ( Notepad++ - its Free! and the installation is ready in less than a minute!)- so no one gets Hurt ! There are two folders Both are named in a way that it is self-explanatory what to do with the contend : Step1 "copy contend in DCS World installation" - do what the folder says says/is named Example path: H:\Program Files\Eagle Dynamics\DCS World\. Step2 (optional) "copy contend in Saved Games to use a preset of snapviews" - do what the folder says/is named Example path: C:\Users\>YOUR USERNAME<\Saved Games\DCS\ That's it. PS: Also don't forget to remap the TrackIR Z axis for the Non-6DOF cockpits - so you don't change the FOV when you move your head forward. >>> http://forums.eagle.ru/showthread.php?t=105515 ---- Info how to change min/max FOV aka Zoom and Neck dimension and more : Open ...\Program Files\Eagle Dynamics\DCS World\Config\View\Server.lua And edit new added lines starting at line #6 - see the annotations for explanation. And read post #1 for better understanding what this mod does when you unsure if you want to do the download , or before posting any questions. Use the attached All planes-modules test.miz for convenient testing.You can start in each aircraft via the briefing menu without having to reload the mission , as they are set-up as client. How to report any annoyances and issues: ...and please read this post before reporting: >>> http://forums.eagle.ru/showpost.php?p=1746236&postcount=126 .

Is this a Quiz? (I love these kind of social entertainment! - this makes me always so exited about new patches!) Set up a wind that goes up vertically at (lets say ) 10 knots - and the pylons will be stiff. Oh wait - What a bummer! - this function doesn't exists in the ME. :) Lets see what kind of possible answer ED has ... - I hope we don't have to take some blue pills to fix it, as the size is already very good.

I know it's very silly and this only a accuse for the usual prejudices... But anyway - I didn't see a long time 'jokes' with cats, so: 14 Hairless Cats That Look Like Vladimir Putin Vladimir , sorry I don't want to offend you - ;) I'm just reposting something... And you will see that my counsellor Merkel looks the same in #4. ...and when you don't like what you see in this link - I bet its easy-peasy for you to block this url. So long... 1. nocoatkitty.com/elf-cats; Time Cover: Platon 2. VYACHESLAV OSELEDKO/AFP/Getty Images; AFP/AFP/Getty Images 3. yamix/shutterstock; DMITRIY ASTAKHOV/AFP/Getty Image 4. thefeaturedcreature.com; TORSTEN SILZ/AFP/Getty Images 5. DON EMMERT/AFP/Getty Images; Bodo Schackow-Pool/Getty Images 6. VYACHESLAV OSELEDKO/AFP/Getty Images; EPA/DMITRY ASTAKHOV PRESIDENTIAL PRESS SERVICE/ITAR-TASS POOL 7. nocoatkitty.com/elf-cats; DAGMAR KIELHORN/AFP/GettyImages 8. EPA/MICHAEL REICHEL; Junko Kimura/Getty Images 9. Alex Rave/wikimedia; Sean Gallup/Getty Images 10. Ysbrand Cosijn/shutterstock; ALEKSEY DRUZHININ/AFP/Getty Images 11. Tomi Tapio/flickr; VIKTOR DRACHEV/AFP/Getty Images 12. tumblr.com/tagged/sphynx; ALEXEY DRUZHININ/AFP/Getty Images 13. Vadim Ghirda/AP; MIKHAIL METZEL/AFP/Getty Images 14. Alexsey Druginyn/AFP/Getty Images

Well, I think ED uses much shorter distances to not confuse the (new)users so much because the Hud will be quickly hidden when you move your head around - and it's a left over of FC2 , that hadn't 6DOF - but its clearly wrong and not what is present in the real world - and when you once have seen a working real HUD you quickly understand . But this doesn't explain at all why they are so different for each cockpit... >>> http://forums.eagle.ru/showpost.php?...7&postcount=17 Read my personal notes on this matter here: http://forums.eagle.ru/showthread.php?p=1588371#post1588371 Further... : >>> http://forums.eagle.ru/showthread.php?p=1739240#post1739240 Well, the HUD on its own is a whole different matter and changing the size afterwards is a very complicated thing once it is installed and 'calibrated' in the virtual cockpit.... Read on and follow the links to get a Idea: Demo for a HUD that works in stereoscopic 3D So things that first seems very simple can get very complicated in the end - just because you tried to 'cheat' and make simplification in the design-phase... I personally still believe that ED choose to make the HUD a little bigger than in real - just to keep readability on low-res Screens. But that is something that now really starts to make huge problems once you want to keep things as real as it can . This would probably a very different case if they choose a different eye/neck position from the start. >>>See all the "how to resize the HUD ?!" threads. (just use the search function - can't list them all - they just pooping out like mushrooms in a misty morning...) ED just better gave this function to the user instead twisting up the HUD size : >>> Big HUD Font for A-10C (...sorry , I'm distracting again) About the 16cm... Well its maybe not the right value in all occasions as your neck is not a static parameter and can vastly change within seconds... We have disused this already (and probably do it again... ): >>> http://forums.eagle.ru/showpost.php?p=1656534&postcount=62 But as long the neck is only a static thing in DCS we have to set it to something like the average of possible distances... -That's the main reason why I want to "rewrite" the server.lua to set global values and make it easy to change them all at once by editing a single value - so noone is forced to use what feels right for me. I have to admit: ...maybe I'm also just barking to the wrong moon...and Naturalpoint-TrackIR is the culprit because their interface doesn't uses relative translations of your eye-position... But writing to Naturalpoint about software-design failures is like writing to Santa and asking for peace on earth ... I tried both - just watch the next news in the TV to see what I got instead.

PS - In the meantime : Follow the info that zaelu and Kuky have posted and concentrate only at the ...Config/View/Server.lua . When you compare the edits of my files in post #1 and the parameters in the restructured 1.2.4 ...Config/View/Server.lua you will (hopefully) quickly understand what to do to restore the old functionality of this modification. Always make a Backup before you change your files and use a proper editor ( Notepad++ - its Free! and the installation is ready in less than a minute!)- so noone gets Hurt :) !

Just a little 'update' of the WIP for 1.2.4: I analysed the new file structure and I have to say that ED is walking in the right direction to de-clutter things and making adjustments easier by putting the relevant functions in only one file (...\view\server.lua). (Well , I'm still struggling to understand the function of the QA-Team of ED by putting out 'patches' that are still clearly in a beta state and break always fundamental things and turn the end-consumer into the position of a guinea pig without a single warning... not able to damage Airborne targets in 1.2.4 with DCS-FC is just one of the worst examples... Having a great workload isn't the suitable excuse for things like this (!) , but now I'm digressing from this topic. (sorry-please don't be so offended - I'm just try to put things in clear words (Heck - I'm German!;)) And I think it has to be said.) I'm now working out global settings that are plausible for all 6DOF cockpits (using the LUA "local" command ) so people that want to alter my changes (once the reworked 1.2.4 mod is up) they only have to change the relevant parameters only once instead of doing it for all cockpits separated. This will also vastly help me to maintain this mod for future patches and lower my/your workload until ED gives us sliders/checkboxes in the options-menu (instead of the inconvenient snap-views saving option that you have to un-look first) ... Yes !, I'm still dreaming of a better world ;). >>> Cockpit View Angle settings in the GUI This will take some time and needs a lot of testing. But I can't take away the need of individual edits made by yourself as you need different settings on a single screen than on a multimonitor setup that covers a wider FOV in front of you. Further: I want and also write a clearly understandable pictured manual/guide that explains the available functions and the relation of your actual view-point in front of your monitor/projection with your Virtual one and the FOV (aka Zoom) - as there I see so many posts where people struggling to understand the fundamentals , what leads into allot of confusion... (e.g.: "Why is everything so stretched at the sides ?!") ...my PM/email-folder is also full of questions about it. And I think that writing a "DCS View System Guide" will help allot of people to understand the limitations and how to counteract them without try'n'error. ...whatever... So please understand that this will take some time, but once I finished it things will become much clearer for you and I will have a reference to answer question by a single 'link' instead of starting always by zero even it has been answered many times before in a similar way .

Thanks ! ... But please stop this rockstar bla-bla... I did nothing up to now. ...I'm just a simple man and I do what I can ;) : Thanks to Klaus Nomi (RIP) for finding the right words ! ...ah, *sigh* ...the 80'ies...

OK Guys, I was finally able to apply the newest patch today (after two days of awful low download connection...) and please give me some time (probably two days) to acclimatise with the newest changes and to rework this mod for 1.2.4 for all available modules and 6DOF cockpits.

Well, I only can speculate as your exact system specifications are missing .... As there are many factors that can trigger this. And you also have to know that Some FPS Massure methods are failing when you use SoftTH. And we are also reaching a point , when using the newest and most capable GPU's that SoftTH becomes useless , because these cards are so powerful that you don't see a benefit against windowed/Fullscreen mode any more. For clarification: I consider to categorise your 1920x1080+1280x1024 as Low-res. On example, when I use such a "low" res setting my own I get worse FpS with SoftTH as when in windowed mode. But it changes dramatical when I use 6monitors in 5700x2160 - than I reach the limits what windowed mode is capable to push through the shared desktop and Fullscren/SoftTH mode becomes superior. I than make a 'jump' from low 20 FPS to stable 30-40 on my Eyefinity 6 HD 6870. So if you really get better FPS with V-sync on and it matches your monitor refresh rate : just keep things like they are and stay windowed (!) and start to enjoy the Sim and stop to look everytime on the FPS counter ;).

Please make your own tests with the collective-brake and the ALt-Hold channel engaged as explained in the flight-manual. Explaining it again in my own words will be just a repeating what I have posted before and comes close to explain colours to a blind person. ... you have to 'see' it with your own eyes to believe it . ;) Yes. - But you don't gradually re-apply it . You just press it down every time you change your rotor-pitch via the collective and you use it also just without changing the pitch to set a new target-alt. See these Quotes from Post #1 for clarification and also re-visit the manual entries - and as always - make your own tests in the sim to get used to it (you will be amazed how stable you can hold your alt while in Hover-Hold mode "hands free" in the cockpit...) : I'm fairly confident that it's a typo and you don't mean the rotor-brake. As you only want to engage it when you have shut down the engines and you park - so your blades don't start spinning by the slightest wind. ...So for clarity sake : We are talking about the Collective Brake in this Thread (not the Rotor Brake).

I read very often posts where people say ( after the usual troubleshooting like "have you controller-conflicts?"/"Do you know how to trim with your stick ?" /ect...) that they are confident how they should use the Trim ( Non FFB stick users ) but they often have still a annoying Bump in their Flightpath and they swear that they use the AutoPilotChannels in the the right way, but they are not able to nail it down what is wrong and they think it's a bug. If you are one of these pilots , please read on and spread the word: One major factor in the KA-50 for a stable flight path ,after the cyclic-trim and correct use of the AP-Channels , so you are able to fly almost 'hands-free' and allows you to put all left concentration in managing your weapon and sub-systems is the Collective Brake. The Collective brake is not only a cosmetic gimmick in the cockpit - it has to be used nearly as often as the cyclic trim after you made adjustments to your rotor-pitch. -when you use the AP-Channels correctly. The Collective Brake is normally the second most used item after the cyclic trim! You have to use the Collective brake and the Altitude Hold in the right way, together with the Cyclic Trim - and you will see that it will be very easy to hold a wished speed while holding a set alt. Many people that fly the Ka-50 are so focused on the Cyclic trim that they forgot about the Pitch trim or they just simply don't know about it. Using the Pitch Trim aka Collective brake will allow you to set speed and alt. When you change anything in your collective position/rotor-pitch you have to tell your Altitude hold channel about it - and you do it with the collective brake. That is something that just happens automatically in the real thing , as you have to press the collective brake to be able to move the collective... - so it is a no-brainier. I have to admit that it needs a lot discipline to do it properly on a pitch-controller that is freely moving and has no physical brake on it that forces you to press it when moving (like the X-52 Throttle). Having the collective brake pressed = constant signal of the Collective-brake button through DCS. and also disabling the brake that holds the lever in place, so it becomes free moving and has no great friction , so you can make fine adjustments to your rotor pitch as needed. If you don't - you will always have a very annoying Bump that let you swing like a sack when reaching the limits of the Alt Hold channel. Further : And this can than be the key factor why you are not able to bring down your un-guided rockets/bombs precisely. I made myself a collective that has this Brake functional so I'm forced to use it in a proper way without thinking about it at all: >>> http://forums.eagle.ru/showthread.php?t=86015 , so I have to engage the collective brake to move the collective. - and I have to say using it every time I change may rotor pitch that it stabilises my flight very much and I'm able to hold desired Alt while changing my speed without problems when the Alt-Hold AP-Channel is engaged. Please read here to get the full info: Ka-50 Flight Manual Page 84: Ka-50 Flight Manual Page 302: Ka-50 Flight Manual Page 344: Ka-50 Flight Manual Page 483: I Hope this post helps you out to sort some issues you are still having after years of flying the Ka-50. And here you will find another very useful "stable-flight-path-helper" that corrects a software-design failure as good as I'm able to : How to unchain the rudder from trim - solution And/Or just read my whole "Standard Ka-50 newbie reply" ;) : http://forums.eagle.ru/showpost.php?p=1619851&postcount=14 Another good explanation: ...and a MadDog-IC shows you how to program a script that automatically press the collective-brake for you whenever you move the collective. Start reading here: >>> http://forums.eagle.ru/showthread.php?p=1800980#post1800980

First : Sorry for the late response , but I was very busy the last month(s) and today I start to see a light at the end of the tunnel I'm walking in... ;). Well, you can read about the proper function of the collective brake here: Collective Brake - aka Collective Trim ... and why you should use it. (I just opened a new thread about this matter , as I think it isn't discussed enough on this forum how important this function is) In a nutshell: Having the collective brake pressed = constant signal of the Collective-brake button through DCS. and also disabling the brake that holds the lever in place, so it becomes free moving and has no great friction , so you can make fine adjustments to your rotor pitch as needed. Well, I really forgot where I found the the gears for the twist-handle , but I'm used to collect gears whenever I see them on stuff that other people are used to throw in the trash-bin. I have now a wide collection of different gears that I can use for my projects. Here is one example(I made the picture just today): The picture below shows the trash-bin of the company I'm working for. It's a used/empty cartirde for for a laser printer - and as you can see you will find on it different high-precision gears in various sizes, that you can use for things like a twist-grip and many more after a small modification. Further: Here you can see how I modified the collective with a counterweight to make it work for the Huey ( and I will temporally disable the function of the brake) , as the Huey (that will be simulated as DCS module) has no automated stabilisation system for the needed rotor pitch and you are forced to move it much more often as in the Ka-50 to keep the right altitude. ... and having to press constantly the brake will be very inconvenient when sitting in the Huey.

Yes , please mail it and don't zip.(the exe is already highly compressed) Just rename the exe to *._xe or something of your choice, so it will pass all e-mail filters. Mail to: Many thanks!

I'm searching for the iZ3DDriverSetup.1.10b3 (1.09.0034) Please don't post the Chinese links that don't work: been there - done that. Can a kind soul upload this particular driver?

Great Job and thanks for your spend time to have a look into it and the tutorial . About FC3/Su25T: Cockpit devises are hard-coded. Only ED has the power to fix the HUD for it.

When these said developers aren't interested themself in this technology and not interested to have at least one unit in their graphics department, and they also aren't able to make the rendering ready for plain stereoscopic 3d (separating the 3d world from GUI elements and the community even does the bug-fixing : DCS world BS2 true stereoscopic HUD and howto ),.. well , maybe they should rethink if their developing strategy is consumer and future orientated.

Can confirm it - the Stick shakes nicely between my legs/hand when gears/flaps are down and high AOA.

Script example : Zoom-In/Zomm-Out on PAC1 to make your life easier ! and another one: http://forums.eagle.ru/showthread.ph...44#post1621544

...first multi-monitors and now this crazy attempt to get the user into the environment, ...yeah, exactly- it's sure too much asked that ED makes his homework and clearly defines what is menat to be a 2d object or drawn in 3d...

Yes , this or you switched off the aero interface while DCS is running. Some VirtualGPUs driver rely on special WDM driver functions to show DirectX contend, and this is only enabled when Aero is on. Please make sure you use a aero theme on windows level, in DCS "disable aero" is uncheked and in SoftTH 'keepComposition=1". If this fails, I'm out of guesses - I tried USB-Monitorts some time ago and was not satisfied at all. Well, things can change when there are USB Monitors with USB3 support , but as long it is USB2 I wouldn't recommend it at all. Cheaper and much less hassle is to us a normal VGA/DVI monitor with a second cheap GPU and you would have even more room for additional gauges/info.

Sorry, no cake for you, if the rendertarget is bigger as your Mainscreen/3D Vision arrangement. And keep in mind that the lilliput 8" USB monitors will also add a extra burden on your system as they install a VirtualGPU that acts as 'man in the middle' between your GPU and the USB Bus.

please google avira+false+positive. ...and while you on it , also google for a better virus scanner.

Of course there is something going on ... But if you can also see it with your own eyes while sitting in the aircraft , there is sure something wrong with your neck and the natural ability of your brain to cancel out this shaking. Please make a simple test next time you you wash your cloth: First just simply sit on the washing machine while it is in a high spin ...and than press your head directly against it ,to see why the camera shakes. :) Serious: Simulating such vibrations via visuals is plain wrong. Get a buttkicker instead.

So here comes my "standard Ka-50 newbie reply" : First download Bigfoots interactive training missions >>> KA-50 Black Shark 2 Training missions Read also besides the manual this: DCS: Black Shark... Technical, Simplified -Coaxial Rotor Aerodynamics -Trimming the Ka-50 Black Shark <<<!!!! very important to understand this fully! -Part 1 - Autopilot <<<this too! -Part 2 - Autopilot and when you are confident about your cyclic-trim, you want to read about your rotor-pitch trim (aka collective brake): Is it even possible to maintain speed and/or altitude? And when you still have time , read this too: A Stick and Rudder Man's Guide to DCS: Black Shark Here is a useful tweak if you using real rudders*: How to unchain the rudder from trim - solution Things you want to have some day too: KA-50 collective: another picture-tale Two MS FFB2 with Cougar Grip Welcome aboard! *and if you use a FFB stick or not the "Central Position Trimmer Mode"

I run also a 32bit copy - so I'm able to examine bugs that some users 32bit users are reporting. But I voted for 64bit. EDIT: ...I hope that the next time a developer starts such a important poll like this he thinks about the possibility to add a third voting option ... I think something like this "I run both , 32 and 64 bit" , would help vastly to make the right decisions.