JEFX

Great, my pleasure! JEFX

I suggest recalibrating your throttle so that it goes really from 0 to max (if, by any chance, your throttle is badly calibrated and when you start your engine it is already up by a certain %, despite it being physically at the minimum, you may have problems). JEFX

Hi! I once wrote a little guide, are you reffering to this by any chance ? http://forums.eagle.ru/showthread.php?t=68334&highlight=jefx good luck! JEFX

well well, all this doesnt seem very scientific...:music_whistling: The reason I didnt patch yet is to avoid tweaking everything again... Is it known if there is a file or two that we can just keep and copy-paste in the patched version ?? ex.: snapviews.lua? config.lua? And what is the file for the keys assignements? for the HOTAS assignements? thanks

well, I didnt know that... I always find that when something works great (and the RC works REALLy well on my system) I hesitate to change it... Patches often mean calibrating, changing things, opening up the config files, reassigning axis and buttons on the HOTAS, making new snapviews, etc... a pain, especially that I have little time to fly due to work... Do we need to reassign everything with the new patch? thanks JF

forgot to say : I am using the Release version (no patch yet). no mods. JEFX

I have tried a few times to access some MP servers and I always get a message : ''fail integrity check''... The only things that I havec changed in the config files are the following : IN config/view/view.lua line 126 ''cameraviewanglelimits'', I changed the second digit here to 175 in order to have my wider field of view with my TripleHead2Go and lines 49 and 50 both to FALSE in order to record my own snapviews also IN config/view/labels.lua I changed all labels to a single '' ' '' and I changed both colors so that they both appear grayish-black (that can help SA but not so much... sometimes to learn...) I think that this is all I changed and still I get this integrity check fail...:( ??? any ideas??? thanks in advance JEFX

Warrior What is different in the Startup sequence or details from Beta to Release? Thanks!

As says =ACU=, there is no need anymore. And furthermore, on a 64bit system, the 64bit version of DCS A-10C works even better! JEFX

...actually this one is quite easy compared with some that we have known in the past...:music_whistling:

Thanks, merci =ACU=, I thought that it could be handy for those who have less experience with what has become known in the whole Flight Sim's history as : The Dance :smilewink: Jean-Francois

Sorry guys, my mistake, dont defrag your SSD, I meant your normal HD. Just edited the mistake. THanks

JEFX’s GUIDE : HOW TO TRANSITION SMOOTHLY FROM BETA VERSION TO RELEASE Please, allow me to make my small contribution here. Every time I went from one version of LO or FC to another, or from one Beta to the other, I was contemplating the idea of a clear and complete method to do it without forgetting anything. Therefore I made myself a small list and I want to share it here. Feel free to correct or comment if you will. Getting the appropriate files : Of course, first and foremost, download from the main DCS website the Release Version of DCS A-10C (all 4 files, placed anywhere on your HD, but IN THE SAME FOLDER) If you do have a 64bits W7 System and had to fly DCS A-10C only in 32 bits before because of TIR not working, they have now an update to their software that allows 64 bits games to run, you get it here : http://www.naturalpoint.com/trackir/06-support/support-download-software-and-manuals.html I suggest software version 5.1, it works great. I can tell from my experience that it helps the performance to go from 32 bits to 64 bits, therefore I wouldn’t hesitate to use it now that Naturalpoint have upgraded! Upgrading TIR : (if necessary) Uninstall (using the remove program control panel of windows) the previous version of TIR software but before that, do keep a copy of your profiles somewhere, they will work in the version 5 of the software. Instal the new software version of TIR and once installed, click on the update button to make sure you have the very latest of everything. You can now copy back your old profiles in the new profiles folder of TIR 5. Some people have had the experience that the software was not seeing their camera (no device found…) : if this happens, simply unplug the USB cord of the TIR camera and plug it again (perhaps in another USB port, it helps sometimes for the computer to see it… stupid windows…) Take note of your changes in the config files : (very useful) If you have made any changes in any of the config files (ex.: view.lua), it is now time to jot them down in order to remember exactly and use them again in the new config files that the program will install. For those with TripleHeadToGo, for example, they need to change, in config/view/view.lua, line # 126 from [20, 140] to [20, 175] in order to allow for the wider field of view. Also in server.lua, line # 119 from [140, -65, 90] to something like [200, -120, 90] or so (bear in mind that I am talking about the new line numbers of the installed Release version). If you like to use your own snapviews like me, you will want to take note to change both (new) lines #49 and #50 to false (DisableSnapviewsSaving AND UseDefaultSnapviews). Since this is now the first release version, I would not keep any old files but remember that, once you will have saved all your snapviews using RAlt-KP0, you might want to copy the snapviews.lua file for later patch instal. If you like to tweak you labels, remember to take note of what you change. For example, may of us like to change ALL labels to a ‘ only which can help a little SA without cheating too much (at least to help learning the beast). This is done in config/view/labels.lua lines # 31-50 (new numbering) by changing what is between the two quote signs by the character that you want. Some like also to change the color of the labels to a neutral color that doesn’t show the sides. For a nice grey that is really not that evident to spot, that can be done in lines #54-55 (ColorAlliesSide and ColorEnnemiesSide) by changing both to [65, 85, 45]. Keep your screenshots : Of course, you will want to transfer the content of your screenshots folder somewhere before reinstalling the new version! Keep your custom missions and campaigns : You will also want to keep a copy of your user made missions, for future use, but bear in mind that they are not supposed to work very well from beta 4 to the release version. Later, from Release version to a future patch (if any…) they might work better. Take note of all your options settings in game : Take note all the system options that you have settled for recently (texture, scenes, water, visibility range settings, etc…). Since those simulators have a big demand on computers and systems, one is constantly experimenting with settings in order to get the best compromise between beauty and realism (some call it eyecandy) and performance. You will want to set your new version (release in this case) to the exact same settings in order to compare performance. I even suggest that you run a simple mission (take of from say Batumi with no clouds, etc… and jot down the fps in cockpit, outside, etc… Take note also of all other pertinent options (sound, etc…) that you might like to tweak in the same manner in the next install. Take note of your keyboard assignments (if you changed any) and your HOTAS axis setup and button assignments (including curves, Toebrakes inverted, etc…). Uninstall the beta version : Once you are sure that you don’t need anything from your previous version, uninstall using the Windows uninstall programs control panel. Then, manually erase all remaining shortcuts, and even the Eagle Dynamics Folder in your Program files Folder should be deleted, some folders and files are leftover from the uninstall process. I suggest then to clean the system and the disk a little. The best app for cleaning is from Piriform and is called CCleaner (it is totally free and very well known). You get it from here : http://www.piriform.com/ Once you have it installed, you can run both the Cleaner and the Registry cleaner of this wonderful program. The next step would be, if you want, to defrag your drive from which you operate DCS A-10C. This is important because it can slow down the usage of the software a lot. Another great tool from Piriform is called Defraggler and you get it free from the same site. Run it and defrag your program files drive (defrag your ‘C’ drive but not your SSD if you have one). Install the release version : Once your computer is clean, you can now install the new version (do let internet running at the same time, this will automatically ensure that the DCS website sees your serial number, if you are installing on the same machine as the Beta version was installed. The process is the simplest possible, just click on the setup.exe and it installs the whole thing automatically. Backup your new files : Before you do anything and even run the program for the first time, I strongly suggest that you copy the content of the whole DCS A-10C folder to another location (you need approx. 7 Go of free space somewhere). Believe me, it can come in handy if one file gets corrupted or you messed up something with a tweak or a mod and you want to revert to the old file without having to go through the hassle of reinstalling the whole thingy… Set-up your config files : It is now time to change whatever parameters you want in your config files (field of view, snapviews settings, labels, etc.) according to the notes that you have taken. Run the software for the first time : You can now start DCS A-10C. If you have done all those steps well (especially uninstalling completely and deleting all unnecessary files), you should not have any problem running the program, it works like a charm. You should now go to the Options settings and dial back all your previous settings, (system, sound, game, etc… Axis settings, curves, etc…) There is a !bug! that one should be aware of : you cannot try and bind a key to something new if that key is mapped to something else in the long long list of key binding : it crashes the program CTD. Make sure you unbind the key before you try, (use the CLEAR button at the bottom of the window). Always clear the original binding before trying to make your own. Try your test simple mission : Use the ME to make the same simple mission (from scratch, of course) that you had used to test the performance. For my part I was thrilled (like many on the forums) to find my performance greatly improved from the Betas to the Release (it almost doubled my frame rates, and I was able to crank up my settings as well!)… And from here on, the fun starts… :smilewink:

Thanks Nomdeplume, merci! I had overlooked that one.:thumbup: Jean-Francois

It doesnt seem that it is said anywhere in the holy manual how to set up the NMSP for ILS (or TACAN in the same way) ? When I punch the ILS button, the STP button remains selected, do we need to unselect it and just keep the ILS button depressed (and lit) in order to use ILS properly? Could that be responsible for several attemps to land ILS and getting the steering bars crossed nicely just to find myslef offset a couple hundred feet left of the runway? I am right if I sum up the ILS procedure this way (for Batumi, say) : -FLy towards the approximative heading of the ILS runway (in the case of Batumi RNWAY 13 it is 125 degrees, right?) at approx 2000 ft in order to intercept the glide slope from below -on the ILS pannel on the right side, turn on ILS, dial the right frequency (110.15 for Batumi) -on NMSP (front dash, lower pannel), click ILS button and deselect STP button. -on HSI dial the course for the runwy heading (here 125) -follow the CDI bars to get yourself more or less centered on the runway course (before you get the ILS indicators) -at about 7 NM from the runway, you get the ILS indicators in the ADI, keep the bars crossed in the middle (very delicate changes), and adjust the descent rate with the throttle in order to keep the horizontal line centered. (the rest is standard approach : approach speeds, gear, flaps, AOA, etc...) What am I missing if I dont hear the beacons (markers?) thanks JEFX

Hi! all. I wonder if that is right, but I have been experimenting with the wind strenght and direction. If I set up a wind in the Mission Editor like this : SEA LEVEL : 5 m/s and GOING north (meaning the little arrow pointing up on the dial) which would roughly mean a 10 knots wind from the south at sea level... and then 2000m : 10 m/s GOING south (little arrow pointing down on dial) which would roughly mean that at 6000 ft, I get a 20 knots wind from the north. when I fly the mission, I dial up the the WP page on the CDU and then the WAYPOINT sub-page, which gives me the wind speed and direction on line R8 as stated in the manual p. 235 'current wind direction in degrees'. My question is : it seems to be giving me the direction TO WHICH IT IS BLOWING (and it works very nicely, flying down from 6000 ft to sea level, the wind switched 180 degrees and the proper speeds were diplayed) Is that correct? or would it be better that it gave is the direction FROM which it is blowing? (I believe like in METAR)??? thanks Jean-Francois

Wow, this is a great bunch of answers and a very informative thread. Thanks to all, I am looking forward to have the time to experiment with all these. JEFX

Hi all! I really would appreciate any input on your ideas for strategies for the usage ot the TGP... for example, I would make an instant mission with a lot of ground units in them, and I just simply dont find anything on the TGP... Of course, when you know where to look it is easy (for example, when a JTAC message is entered in the system and you get a cue in the TAD, you can make it the SPI, slave all to SPI and LO your TGP will magically be looking at a target... But, in the case you dont... For example, the first mission in THE SHORE campaign... When you get to the green smoke of the downed aviator, it is easy to look at him in the TGP, fine... But how do you go after that to look for threats, to find a good ingress or egress route for the (F10) CSAR Helos, etc... Once something is detected, and made MARK point, or SPI, etc... it is quite easy to work on it, but, how do you look for those targets at first??? thanks a lot, any input will be helpful (I REALLY THINK THAT THE MANUAL IS GREAT BUT IT FOCUSES MORE ON HOW THINGS WORK THAN HOW ONE SHOULD USE THEM...) JEFX

This is just a suggestion for those generous people making great missions for us (such as Greb's great missions or SABRE WIP training campaing, etc...). It would be desirable to post which Beta version these missions are made from since, I realized bitterly, missions are not compatible between beta versions (at least, very often...). I dont know about you guys, but for my part, I decided to skip over Beta 4, since my beta 3 is fine for now (waiting for beta 5). Consider that all those wonderful missions now tweaked in beta 4 might not work in beta 5, etc.... Anyway, this is just a suggestion and another way to say Thank you to mission makers!:thumbup: Jean-Francois

Yeah, same here, I will make it for Beta 5 for sure. Are you gonna update all your missions for Beta 5, because I really want to try them!" thanks JF

No, I am not like everyone else : anticipating each new beta like a xmas gift... I am perfectly happy to learn gradually all the systems and the game with beta 3 and I didt want to go through all the shit of tweaking a new version (controllers, key mappings, and so on), since it was widely accepted that beta4, despite its pluses, is not that great (I personnaly dont have too much performance issues). I decided to wait for either beta 5 or even later... But I must say that your missions look really great... Even enough to convince me to do the change some time in the near future (but I am too busy travelling for work right now, I just get a few hours a week to fly my beloved simulator:()... Jean-Francois

Greb, first of all, thanks for all this effort! I wanted to start playing your missions last night, and I started Southbound and just when I start to taxi the mission Crashes, twice it happened. I am wondering, what BETA are they made for? I am still playing BETA 3... JEFX

John, Did you perhaps wrote DMS in both DMS and TMS schematics?

oh, and by the way, +1 REP to you! Happy new year!

Great, much better, thank you very much, I will use it now on all the time! Jean-Francois