PeterP

Thank you again - I'm happy when you are! Now try this (Instead posting over and over again how happy you are ) : 1. look out for this > < button in one of my posts (in the same row where you see my avatar) 2. Click on it! and make sure that in the pop-up "I approve" is checked! 3. Add some nice words/sentences. 4. When you are done - Press "Add to reputation" Thanks! BTW: Check your user-CP and you can see what I wrote to you while adding 86 reputation points to your profile. (after earning 300points from others you will get +1 ) Now please don't think that this is what I'm after - but its quite nice from time to time to browse through your profile and be able to read from persons you never saw in a thread you have posted, just how happy they where to get some info from you... I hope you get my point. Have a look to know what I mean:

DCS 1.2.4.12547 doesn't carry over the Default Snap-views values when Customising. So when you change the View.lua file that has "UseDefaultSnapViews = true" to 'false' - DCS doesn't looks for the default values to recreate the SnapViews.Lua in the savedgames path any more - DCS just uses 60°FOV and all other parameter at Zero for all views and each cockpit. When you didn't had a SnapViews.lua from a previous "update" it will mess up all snap and cockpit views and you have to start from scratch! Example - You only want to change on cockpit View for the F-15C in FC§... yes, you can! ...but than you have to re-save the views for all other cockpits and modules. (...) Seriously: ED , i know about developing and releasing cycles and the costs that are involved..., but please! let the QA team (I hope you have one) have a look on a "update" before you push it out. - look at it more from a consumer perspective. The people that raise their voice here in the forum are only a fraction of your users -you know it your own - think about 'average Joe' that don't visits the forum and now thinks that his install is broken and hammers every day a new support ticket in the keyboard...

...three hours of my life are gone again...*sigh* ;) RC 2.21b is UP! ------------------------------------------------ Change-log: 1.2.4-RC 2.11 -> 1.2.4-RC 2.21b -Changed Install instruction to counteract change of DCS Version 1.2.4.12547 see the bug-report >>> http://forums.eagle.ru/showthread.php?p=1769356#post1769356 -More documentation : "DCS Default Cockpit snap-view saving"(LInk to video) example and "Default Cockpit-View preview.jpg" -Edited Un-Install Instruction 1.2.4-RC 2 -> 1.2.4-RC 2.11 -Edited Readme -Changed files so you can use the default Su-33 cockpit -Added Un-Install instructions -Changed initial Huey Pilot view when entering the cockpit - higher FOV 1.2.4-RC 1.03 -> 1.2.4-RC 2 -Four different 'flavours' for each possible module combination -Huey: Reworked Pilot view without tilted sight - gunner views have new limits without gun-collision -FC3: Su-33 will have the fully 3D Su-27 cockpit. Attention ! The Su-33 cockpit will have no tail-hook and glide-scoop indicator! 1.2.4-RC1 -> 1.2.4-RC 1.03 Some changes to the readme and reducing the initial FOV when entering the the Ka-50 ------------------------------------------------ User that where satisfied with RC2.11 (because they probably had already a correct snapviews.lua in the savedgames path before the lates DCS update) and don't have issues with the snap-views saving option Don't have to reinstall this mod! The new added video that showcases how to edit and save a new default cockpit snap-view: (sorry - I had no better Idea how to visualize my key-presses - so I 'tried' to use the OnScrenKeybord - but it works less than adequate -as you can spot-... - please use a real keyboard while you are doing it ;) )

URGENT!: Short update about the "HUD to Close" problem that some report . OK - I nailed the problem down . And It's not my fault! (sort of...) With the newest updates/"Patch" Version 1.2.4.12547 DCS don't uses the values of the "DefaultSnapViews.lua" , to create a "SnapViews.lua", into your C:\Users\>YOUR USERNAME<\Saved Games\DCS\Config\View folder if it doesn't finds there a file. So when you have a View.lua file that has "UseDefaultSnapViews = false" instead of 'true' in it (like the one in my mod) - DCS doesn't looks for the default values to recreate this file any more - DCS just uses 60°FOV and all other parameter at Zero. ( ) This messes up all snap and cockpit views! -whatever- Until I have found a workaround or where this entry for the using of the default values is missing: Step 2 in the instruction is NOT optional any more ! You have to "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\ ...or save your own snapviews as written in the Readme! Will reload as fast as I can a new version that has a changed Instruction.

(Now, you get a Idea why it is sometimes such a pain to write a response to some questions at all... : ) Thanks for this response... but you didn't took the time to answer a single question that I directed at you... Now, instead moving in circles... - please answer only following question(s) : Did you followed the advices to set-up a new Default-cockpit snapview that suits you better at all ? And if yes: Did you used all the possibilities? - I mean: also moving back/forward and Up/Down - instead just tilting the view and zooming /in out ? Quid pro Quo ;)

I did fully understand what you want to say in post #3. And again : no, you can't.

This is impossible! (zooming out without changing FOV - ZOOM is FOV ) You can't brake optical laws. - Its like starting a argument with GOD or the Universe - you won't win. Here you get a idea abort the "why?" (This is the first video of a WIP "Guide to the DCS View-Sytem")

What is this again? - nipticking and starting a argument without having a single one? Sorry ! You are wrong and wrong. If you just want to believe something instead of knowing - well, than go to a church of your liking. Angels are tied to distances when chaining them to a view-system - When you change angels you also change distances - do you know nothing about trigonometry at all?! When you looking at a 3 and/or 2 dimensional projection and you don't keep every parameters the same when comparing it with other projections (e.g Your own View) you will have a mismatch/distortion. This questions are rhetorical - no need to answer them. Please ! Next-time you want to tell me something again like done before here - check your facts and make your own thoughts if it all makes sense before going with it in public. Maybe also ask a friend you can trust beforehand - This will save you and others a lot of time in the future. ...Did I already told that I'm working on a 'Guide to the DCS View-System' ?!... Here is one sneak-peak of one of the videos (WIP) That I'm preparing for it - and it should also answer your questions that you might have and it also should stop this useless discussion. About being Patient: Didn't I answered all questions again and again even the most obvious that are already covered by the readme/firstpost ?! - and you are still not on my ignore-list - isn't this proof enough that I have a lot of patience ?... (Again: This questions are rhetorical - no need to answer them.) Back to Topic!

Version 2 is right now in the works - still issues with the Huey cockpit (Have to re-tweak time- and FOV-limits when the full HDR kicks in)- but I'm very confident that I will have resolved it till the Saturday. ( no -I wasn't able to resolve it.. -see next post for more info) Most noticeable changes are the reworked Sunrays The old version for comparison:

I have some vids - but you will absolute make no clue out of it - it's a thing you must feel your own. EDIT: The only thing I can think off and that would make a little sense : a 1 vs.1 comparison of default and modded - but it's relay takes some time and is a pain - as you can't really just playback one track with both versions - because the view will be totally messed up when switching to a unmodded view.

Than please, please, please, change your default view position like it is written down now nearly 20 times. Further: The default cockpit view is set up in a way that the HUD is in the upper half of the monitor. - just the same like ED did it in their defaults. When you tilt up your view and 'lower' the HUD/UFC , to get the front-dash out of the monitor, the sides get stretched/distorted at the edges of your screen . People, please just start to set up your default cockpit view position your own (as written in the Readme) instead letting someone dictate what view setting you have to use! - sorry that it is not by default exactly what you are looking for - but some people prefer to have a look at the instruments and not only at the HUD - so There must be a 'average' that suits somewhat everyone (yes, there are people that don't use a second monitor for Helios right 'under' their HUD ) - if your initial view is not what your looking for : Read the Readme and take action! I can't do it for you! And don't only tilt up/down ! it is also necessary to shift your viewpoint up/down , forward/backwards - this depends on your own individual sitting/view position and monitorsetup. ...I even wrote the needed key-presses down in the Readme... And read this to get a better understand why the edges get distorted: EDIT: (please understand me : it feels for me that since one week I'm just reposting in this thread what's already written down - so please give me a slack) :):) Now I want to read at least 5 postings from satisfied users in a row , so I can stop banging my head against the keyboard - It starts to hurt! ;) Posting like this: I think you mean 'without lateral head movement', right?!

Thank you ! Here are some general remarks about the HUD in the A-10 that may interest you too (same applies to the F15 - but much more prominent): >>> # 22 and >>> # 17 and >>> # 97 and >>> Big HUD Font for A-10C (can be useful for singelscreen users when setting up a greater FOV (> 70°+) - so you are still able to read the text without to zoom in. BTW: can't do it for the F-15 , as the HUD is Hard-coded )

Do basically what Zealu wrote (well, I have some annotations - see end of this post)- set up a new default cockpit view that suits you. BTW(I can't help it!): it's also explained how to set up a new view in the Readme.txt : EDIT: @ Zalu Your instruction/explanation has some flaws I want to correct: :)

no - it don't just 'goes away' (like a cold) - doesn't my instruction work for you?

..everything is fine and your installation is OK , but you clearly should have some read/web-search how a collimated HUD works and what happens with the projection when you lean forward (and why this is so important for aiming and the right position of nav-points). ...and don't mix up leaning forward with zoom/aka FOV - as your second picture is clearly not zoomed - you just lean forward.

Thanks, Will add a more clearer un-install instruction - this might happens (your quote in bold) because the newly added snapviews.lua of mine gets active and it is not intended to work with the default view limits. You also have to delete this file from your savedgames folder and or recreate snapviews for the default view like it is written down in the readme. But this doesn't explains the 'issues' you have at all . And What exactly means "I have taken ALL the steps" ? I checked the mod twice with a fresh 1.2.4 install before uploading the RC2.11 in all modules and with all flavours in each possible cockpit - and it worked always as intended - the current version is now downloaded over 200 times - I would expect more issues-reports like yours if there would be a failure in the files ... If yo want me to have a closer look I clearly need more detailed info about the exact steps you have made. - so I can exactly reproduce them without the need to guess at all. Example answer I'm looking for: I have DCS World version XXXX installed . And this are the modules I'm using: XXXX, XXXX, ... It was a clean DCS world installation or I have this Mod(s) Installed beforehand/afterwards using your mod : LINKS TO MODS I did choose flavour > put in a,b,c,d < Than I had these issue(s) in cockpit XXXX : Example: A10C Front/Back Up/down Left/Right Info: I'm able to go with my head through the canopy - needs shorter limits. And I wasn't able to solve it by readjusting and saving a new default cockpit view. and so on .... More info = better - I'm not a mentalist or can look over your shoulder. :)

Thank' - but I'm sorry to (maybe) disappoint you. No - will not explain it again. ... I kinda dislike to explain things for each individual that I have already written down. So please follow the quotes/links and pay special attention the the big fat dark-Red words: To make it short: The old legacy 'New View with proper Neck and default 6DOF limits DCS World 1.2.1' isn't compatible with 1.2.4 - and using this legacy files will clearly break functions of DCS World 1.2.4 . Whatever you experience with the old 1.2.1 files in 1.2.4 - it's not how it's intended by me. ( I can only speculated how you made it work at all in 1.2.4...) Oh! - I almost forgot to ad emoticons : :):)

Is it like this ?

Have this sound issue too in various planes/modules. Here is how I can reproduce this bug 100% - in the Su-27: 1. Use attached Mission "All planes-modules test.miz" 2. First Select the P-51D 3. [ESC] > Briefing > Back > Select the Su-27. = whining noise All planes-modules test.miz

Because you didn't read the readme (carefully) and didn't exchanged the the snapviews in the savedgames path. Your snapviews.lua was created before the eye-point moved - and using a default snapview setting with this mod will let you have everything too close. Isn't this simply logical ?! So once again: Read the Readme! EDIT: Well..., I got a notification that my answer might sounds harsh and disrespectful and can scare off newbies...No , it isn't - I only gave the right answer - nothing more/nothing less - in a very compact way , and its not my fault and responsibility if people interpret/underlay my answer(s) with a harsh tone. To counteract it I will try to use the emoticons in the future more often. So please ad this 'mood' to the above response to Yskonyn/All : ;):)

>>> http://forums.eagle.ru/showthread.php?p=1755281#post1755281

This is not melodramatic - there where too much patches in the past that broke the game-play for me - without noticing or hotfix. Much more often it goes like this: Guy: After patch XXX this and that is broken and/or changed. Tester: Already acknowledged. ED-Staff: Sorry, in the internal version it is already fixed - there was no time to bring the fixes in the patch - pleas be patient. I hope you get my point and understand why there is a necessity for threads like this. - I think too that this shouldn't happen and I also don't like them. These-kind of conversations should be only posted in your tester/QA forum. And than reading postings from a tester that he is also surprised that the release happened such fast doesn't makes me more confident that everything is al right. See - I just had a long busy weekend and to day night I have approx two hours for myself and flying. - and I didn't wanted to begin my evening with lots of editing beforehand.

Thanks for the list. Before I apply this patch - does anybody know if there are some new bugs ?

>>> Sticky: "UN pilot" campaign fixes (UH1-H beta) Laivynas

>>> http://en.wiki.eagle.ru/wiki/All_about_your_account