sc_neo

with MMJoy2 you mean wiring it to an arduino board and stuff?

I reckon you can 'fiddle' the grip on the t.16000 base and have two devices show up in dcs. Or maybe one can really hook up the grip connector to the t.16000 base electronics...Virpil guys sure know whether its possible.

a short question concerning the standalone grip. Is there anyway to connect hte grip directly to the pc without the Virpil base or Warthog base? I've got the t.16000m and therefor have a lack of buttons and switches. The stick-base combo is more what i can spend atm and getting the grip only would be a good start provided you can hook it up directly to the pc somehow. Any idea on that?

got the older green t.16000m and added to it the FCS throttle. Would you care to specify what you mean by control profile? I don't use thrustmasters TARGET software at all since my stick does not have any wiggle in the centre position. Or do you mean profile for specific dcs modules? In that case, i think you are better off taking the time and setting this up by yourself. Easier to remember und its all the way you think fits best. Its a nice and very presice stick...have fun with it.

Looks great man. Really looking forward to the next version including the ndbs. Up to now you had to make a choice whether to have a modded beacons.lua active that either gave you ndbs or rsbns...and switching around depending on which aircraft you fly isn't the greatest thing. The latest 2.1.1 release linked in you second post does not contain any txts or info on the different RSBN/PRMG channels, where can i get the latest files on that?

Ich persönlich hab erst 2016 direkt mit Nevada angefangen und fliege eigentlich nur dort. Sozusagen 'noobschutz' im Testgelände. Ich hab zwar Bartheks ground textures, aber Caucasus wird für mich erst mit 2.5 interessant. Für mich is das son immersions Dingens. Erst in NTTR die Maschinen richtig lernen, dann im Kaukasus die Kampagnen ''in echt machen''. Ich sehe im Schnitt jetzt immer so 10 - maximal 15 Nevada server online, aber unter 170er ping zu den US servern ist nicht drin. Der offizielle US 'Through the inferno' hat zwar auch 200er ping, is aber vom setting her ganz brauchbar. Diese Mission müsste man halt mal in Europa oder DE aufsetzen. Sind hier im deutschen Teil des Forums ein paar Gazelle Piloten unterwegs, die ab und an coop machen?

tach Leute, gibts eigentlich auch nen ähnlichen deutschen server für NTTR? Hab mir neulich erst die Gazelle geholt und coop in Nevada mit gutem ping wäre schon was!

then this thing really is a coop multicrew vehicle...:)

In Chuck's great guide on the Gazelle he writes on page 78 in part 12: ''HOW TO USE HOT3 MISSILES (SA-342M) 10) Ensure all preparations on previous page are done. 11) Fly towards target and come to a hover from a concealed and safe position. 12) Engage auto-hover as explained in the AUTOPILOT & TRIM section. 13) Turn weapon key to either JOUR (Day) or NUIT (Night). 14) Select desired HOT3 station (1/2/3/4 = stations, 0 = safety) 15) Use TV slew controls (; , . /) and Zoom knob (= - ) to find desired target. 16) Lase target to lock it and range it. A white rectangle will appear. 17) Press “Auto-Slave Toggle” (“E”) on pilot’s stick to automatically steer the helicopter to the slaved target you just lased. 18) Optional: set Camera to “ASS” (Asservi = Slaved) to track target with camera. 19) If all launch parameters are met (range under 4300 m + target lased), missile launch is authorized (BON/OK lamp illuminated). Press “Missile Launch” button (Space).'' Is that an actual feature of the Viviane system (i can get it to lock on a position but not to track a moving target myself) or did he type that up a bit ambiguous?

I got her for a couple of days now, and without trying to overly pad myself on the back, i had no problem getting her to do what i want from the get go. I must say that i spent a couple of hundred hours flying light helos in an aspiring combined arms game/sim that got an advaned flight model sometime after release and this taught me all the building blocks for properly controlling and countering the various forces when lifting off and landing in a light helo. I gotta say that i was quite relieved that this transition went so smoothly...boy, i thought i would have to spend hours and hours to get the tiniest thing right. Landings with that weird sliding like on ice is a bit off still, guess that will be fixed some day.

So is this mainly useful for mission designers as a base template to not have to start from scratch every time ? Or rather for personal free flight sessions?

Looks great for sure. I trust work on the conversion for NTTR is going on in the background as well, so we finally have campaigns that befit the name Nevada Test and Training Range. Any new infos on that you might share with us?

i am not too familiar with the HUD symbology...is there a symbol or something that shows whether a recovery system kicks in? I only see the fly up warning...

Hey lads, In case a pilot blacks out during high g maneuver: do ''modern'' jets have some automatic blackout/redout recovery mode or such, where it automatically steers the jet onto a stable, horizontal flight path until the pilot becomes fully conscious again?

Lgbs for instance...thats exactly the kind of info i was looking for in my op. So in the A-10c you can alter some parameters like autolase time, laser code and such. Does the F/A-18 weapons menu system for this class of bomb and how you change variables look similar or alike how it is presented in the A-10?

thx for the infos guys. I guess i'll see the first taste of what lies ahead with the introductory videos....

So i was just wondering: how much of the specific A-10c knowledge (not general airmaenship) will be applicable for operating the F-18c. Startup procedure, radio, HOTAS, CDU?, Weapons systems, MFDs, and all the rest.... you understand what i am getting at. Are all of these systems fairly similar or do i need to carve out a completely new ''grey cell library section'' to store all that new info in?

and is he not involved in baltic dragons A-10c training campaing somehow as well?

hrm, not easy to decide in the poll i think. It really depends on the state of the terrains by then. Especially, nttr might have moved from alpha to beta/stable by then were as caucasus might barely in alpha status. Then again, naming doesn't matter as long as the content works for the most part.

Is it possible to run this together with the Extra NTTR beacons mod? Both add a new beacons.lua so i am not sure whether its possible.

@Sokol1_br Well, nice write up and destruction of my dreams :) Good explanation, thx. I did not know that the vkb uses proprietory code and that the entire sensor/wire setup neede to be replaced. Anyway, i can't justify to spend that amount of money atm that it takes to get the gunfighter dryclutch version. You are looking at around 450$ for the overall pacakge. Maybe some other time then. Which means...i better get cracking with the t.16000m 'Frankenstick' mod.

The Pro model would solve all my problems and should be a permanent keeper I reckon. Hrm, the question is, can I somehow hook that thing up to the base of my t.16000m without damaging or outright destroying the new grip in the process. So I gather that all the electronic PCB boards are not placed in the grip but in the vkb or thrustmaster bass units and wiring the Trio to anything other than those is a gamble?

Did you double up on these 6 buttons with one of them becoming a modifier key that is wired to the other 5 buttons with a resistor in one direction ending up with 10 instead of 6 buttons? If so, does it work ok?

Yeah you and i were talking about that in dec/january in the 'finding the right switches' thread. Sokol, what do think is easier for upgrading my T.16000 to the kind of 'Frankenstick'. Going the migration route with a resistor to make one button a modifier essentially ending up with 22 new buttons? Or would be less hussle just getting a 10 dollar micro pro board and adding the buttons i need as a seperate DX device via mmjoy? For the latterm, i wouldn't have to touch the t.16000 boards, but would have to 'read up' on mmjoy and arduino stuff.

haha ok. I plan to upgrade my T.16000m to be fully equal to a Warthog button/head wise by canabalizing those 12 bottom buttons and adding a bunch of 4 way switches and buttons at the joystick top. My plan is to make one of the 12 buttons a modifier key which is wired to all remaining 11 buttons (with a resistor in one direction) to end up with 22 buttons in addition to what the t.16000 has at your finger tips already. When i read about that mmjoy-arduino business, i just hat a wet dream of buying one arduino board and having 128 buttons including 8axis to play with...hooking up all buttons i liked to the T.16000 without tinkering with its electronics and in the process, maybe building a helo collective later. But as you guys suggest, you end up with just enough to setup one device properly. Still, very interesting, especially once i think of building a collective. Hrm, i just have to read a bit more to make a could call on whether to follow through with my original plan of using the 12 bottom buttons of the T.16000 or leave that as it is, and add all the stuff physically on the joystick but wire it seperately with mmjoy. It'll be cheaper for sure. Which is more practical you think?