sc_neo

Might you consider making a black version of the Viggen english cockpit, like the F-15 black cockpit mod? I believe this must look badass!

@Art-J ...totally forgot about this command and console thing! Works like a charm, thx man.

huh...i'll do it the lazy and patient way. I just wait till 2.5 release shows up and transform 2.2OA into 2.5 release...and thus hopefully retain 1.5.8OB for as long as i need it (or transform the latter into final).

roger, thx.

Yeah: simple question; how do i end up with 2.5OB and 1.5.8 final when i have 1.5.8OB and 2.2Alpha installed atm?

that stuff is a complicated mother....

by the way: whats the best way to totally clean a DCS game folder from any changed/altered and added files? The repair function seems only to replace changed/altered files and moves those to the backup folders. But added files like liveries etc. that did not replace any vanilla files, is there any way to clean those out automatically? Can't find my file where i noted all the changes i made to the various DCS installations.

@Yurgon ...thx. And the standalone installer tomorrow, will that one leave 1.5.8OB alone and only copy necessary files from it? I wonder, i probably could make a copy of the 1.5.8OB folder ''update this'' to 1.5.8 final after i have updated the original folder to 2.5OB.

ATM, if i update 1.5.8 openbeta to 2.5OB, will i be able to keep 1.5.8 OB via promt or is it going to be consumed during the update? Cause i still need that and i kinda don't want to download 1.5.8 final only to finish a couple of missions i still need to finish on 1.5.8 openbeta.

Whats your best guess: concerning cummunity made missions for 2.2 NTTR and those working in 1.5.8 Caucasus; is it save to assume that the ones for 2.2 NTTR will work properly in 2.5 NTTR since the map has not changed from 2.2 to 2.5? Thus it should be save to delete 2.2 NTTR after 2.5 is completely installed? I reckon coummunity made missions for Caucasus 1.5.8 won't necessarily work in Caucasus 2.5 unless they are simple A2A ones. Thus it might be a good idea to keep 1.5.8 around until i have either finished them or they have been ported by the respective designer?

i am excited about the reiteration of the 'ongoing work to implement Vulkan Api'. Whether this will deliver great improvements from the get go, who knows. But its great to see they are not wasting time let the engine be stuck with dx11 for years to come.

Also ich hab vor knapp zwei Wochen meine TM TWCS, die ziemliche stiction hatte, mit Nyogel 767a gefettet. http://www.micro-tools.de/Fette-OEle/Fett-stark-daempfend.html Das kam zu knapp 25€, inklusive Versand, und war nach wenigen Tagen per Post (nicht DHL) im Briefkasten. Scheint aber grade wieder vergriffen zu sein. Das Zeug hat das Problem bei dem Schubregler komplett behoben. Ist aufgrund der Dämpfung natürlich etwas schwergängiger. Aber das Ding lässt sich jetzt absolut stufenlos und fein fahren...ziemlich verblüffend. So sollte TM das eigentlich ausliefern. Meinen Warthog muß ich auch noch damit bearbeiten. Hoffentlich reisst das Dämpfungsfett dort ebenfalls Bäume aus.

VKB and VIRPIL, you hearing our screams?

@dimitriov ...thats fine, of course, take your time. I have post poned the campaign for 2.5 until now, couple months more doesn't bother me. Although i'd be interested to know whether the conversion for 2.5 (this is mainly aimed at Polychop) is contractually mandatory for 3rd parties or simply ''good form'' as a developer...so to speak good advertisement for your brand so that customers know they won't be left in the dust. I would imagine there are some contractual clauses that specify how a module's upkeep costs are shared? Buying modules for DCS kinda goes with a promise (at least thats the expectation i reckon) that modules, with everything that accompanies them, will be kept in playable shape pretty much for as long as DCS is commercially available. And i do get it: the beauty of DCS is its constant development and that things you buy today will be more awesome couple of years down the line, or at least the overall experience of a module in it's environment that is. And these upkeep costs, that are probably significant when such a big change/advancement like Caucasus 2.5 hits, are not easy to calculate beforehand. Again, take your time. Better have a properly transferred version later than a poor one now!

How much grams of Nyogel did you use for the Warthog stick? I kinda don't want to waste too much....but it should get the job done of course.

jetzt muß ich mich gut am Stuhl festhalten und eisern bei meinem Plan bleiben: erst die F-14....und erste einige Zeit später die F/A-18! Sonst komm ich irgenwie durcheinander :)

To give credit where credit is due: i disassembled my TM TWCS throttle yesterday and cleaned it from all grease (gave it a good rub with cleaning alcohol just to be sure). I then applied the often mentioned Nyogel 767a and its true....stiction, which my TWCS fairly strongly had due to its rail design, is completely gone. It just moves completely fluidly, minuscule adjustments are a joy, not a chore anymore. Wether the heavier feel and slower movement (you can't raise and slower throttle inputs quite as fast as before due to its dampening nature, that was rather the point huh :) ) is considered a pro or con, is for everyone to decide themselves. Might be a little bit slow for helicopter flying, perfect for jets. On the other hand, it provides for the tiniest adjustments when hovering in a helo and janking your throttle/collective is seldom a good idea anyways. We'll see how this stuff holds up over time. I'll do the same with my fairly new Warthog stick. I ordered from http://www.micro-tools.de/OEle-Fette/Fett-stark-daempfend.html which has it on offer in Germany. Was about 25 euro including shipping for two oz or 56gr. Anyway, this is how TM should ship their products in the first place! I reckon it would be quite cheaper for them to order that stuff on industry scales. Besides, it takes about 1-2 grams for said throttle, probably a good deal more for the Warthog stick. Still, that would not increase the price in any way worth mentioning, not considering that the input unit you buy only becomes really usable after applying it.

Hey Winston, will you update Steel Winter for Caucasus 2.5 provided it breaks some stuff like units placement etc.?

Come on Vripil...go....give us some more info! Price estimate etc. My Warthog needs a new friend!

Wofür und warum sollte man Intel dafür in Regress nehmen können? Da müsste doch schon nachgewiesen werden, dass Intel besseren Wissens 20 Jahre der zu Liebe Performance diese Angriffsmöglichkeit zugelassen hat. Könnte ja auch ein back door sein.

Naja, laut VKB soll sich ja an der Verfügbarkeit bald was verbessern. Zum einen planen die auch in Europa dauerhaft bestückte Lager an den start zu bringen damits nicht diesen ewigen Kampf um die 'batch' Produktion gibt. Außerdem wurde doch heute erst erwähnt, das ein voller Kontainer nach EU unterwegs ist, der alle Preorder sowie ''erwarteten Absatz'' der nächsten sechs Monate decken soll. Ob das nur für den MCG oder auch Gunfighter Basis gilt, kein Plan. Die wären einfach blöd wenn alle heiß auf deren Produkte sind, und sie immer einfach nur zu wenig produzieren. Zumal der MCG ja als VKBs Standardgriff für lange Zeit (Immer?) bleiben sollte, vielleicht komplementiert durch einen mit westlicher Anlehnung und halt speziellen derivaten ala F-14 etc.

about the slider vs tilting one: i have the TM TWCS and it certainly has a good amount of stiction which i as of yet still have to remedy with Nyogel. So i guess sliders are generally more prone to stiction than other designs. But, i always wondered, how a tiling throttle actually is set up internally?

What they (if feasible) should do, is to design input devices where you have generic, empty 'sockets' instead of already pre-installed buttons, hats and switches. The customer then orders the throttle and with it as many hats, switches, buttons and places them in whatever conifig he desires into those sockets. And, if one day a hat or so goes south, you simply install a new one without even having to opening up the entire device. For instance with the TECS, i personally would probably install another 4 way head where that grey lower thumb button is installed, and the same with the grey front button on the right throttle.

Hrm...the TECS looks promising. But in my book, not ''overloading'' the throttle with hats and switches sounds 'reasonable' at first, but i have just imagined how to assign the A-10c throttle functions on this one. And, it seems to me we would be missing at least two more 4 way hats for good measure (one in front and one on the right side). Yes, the MCG grip series has enough to transfer the missing inputs from the throttle to the stick, but i honestly prefer to keep it bound to the correct input device. Could you post an image of the left side of the throttle? Is there some switch or hat or something like the A-10c's pinky switch? Again, would be kinda the same wasted space like Virpil seems to forgo with their throttle design. And yeah, especially if you mention 'VR potential' as one deciding factor, then there should definetely be as many hats/switches as ergonomically possible on the throttle so you need to fumble around blindly only for very exotic functions. Anyway, looking forward to this throttle! BTW; is that black circular thing on the left throttle a rotary axis for zooming for instance?

Wags, Thank you for updating us on ED's current thinking on this one and i welcome this idea very much. Looking forward to a proper explication of everything related to the new protection system. Makes me anticipate the F/A 14/18 much more :)