sc_neo

The divert page on the cdu shows that sweet arifieldinfo like TWR freqeuncy, runway heading etc for the 4 closest airfields. Is there a cdz page to look that info up for all the other waypoints or airfields in the mission waypoint database, or do we need to rely on kneeboard charts for that? Additionally i'd like to know: when i control the cdu via the ufc buttons and look at it in the mfcd, how can i switch between page 1 and 2? The cdu has that p1/p2 rocker, can't find something similar up at the ufc though. Would be really handy.

Q: Will the NTTR converted basic and advanced training qualification campaigns be free of charge for owners of the original ED store Caucasus campaigns or will this cost a bit extra?

wow, thanks for that great illustration! Did you just draw that up for me? It's a really straight and simple design, and the idea with the diodes is great. I am a bit busy this week so i won't get onto the case right away. I hope i can ask for advice when i actually start my little upgrade project. Cheers mate.

nice build :) Did you add a second stage to the gun trigger up fron as well? I don't quite understand how i could turn the orginal 4 way HAT which acts as an 8 way HAT into 2 four way HATs? I guess there aint't 8 wires going down but the pcb sends different digital signals for each position. Could you elebarote a bit more on how this '4/8 way HAT' could be modified into 2 seperate 4 way HATs?

@Sokol1_br ..... thx a lot for the help. The stuff at http://uk.farnell.com is pretty much what i am looking for. Making the actual head from a piece of wood or whatever ain't a big problem. Its really weird, the actual 4/5 navigation switch costs less than a pound there...but complete with an actual head on them nothing less than 16$ pops up. Yes, real estate is tight on the T.16000m. Unfortunately the big 3 grey buttons at the top of the stick are not siple push-buttons but seem to press against a cb. The slickest way to do it would be to place the 4/5 way navigation switches at these exact spots (where the 3 big greay buttons sit now) and canabalize their function for the click function of the 4 way switch and run 4 wires from the base buttons upwards to feed the 4 directions. Additionally i'd love to steal 4 inputs from the POV / 8 way head thats already there. I really have a hard time to consistently push the diagonal directions...hence pretty much i use it as a simple 4 way head in the end. The T.16000m has 24 ''clickable'' inputs overall in addtition to its 5 analogue axes. Thats a lot to work with and in its vanilla state, its really underutilized. If you know of a thread/post by some who made such a comprehensive mod to a joystick please let me know. I guess i have to look a bit more into what i can actually comfortably re-use from the T.16000m before ordering something. You pointed me in the right direction to get started, thx a lot.

The T.16000m has a lot of 'unused' buttons on its base and there are a couple of button mods that add a pinky switch or designated 'lase button' by soldering it in parallel to the aforementioned buttons that are most of the time out of reach. I was wondering, would it be possible to add an additional 4 way head to the T.16000m? There's 12 buttons on its housing that i don't really use. I have looked around but did not find any 4 way head buttons to buy. Any good store that sells those come to mind?

Du vielen Dank für die infos und Ratschläge, aber ich glaub ich lasse das und hole mir gegebenenfalls doch die neuen Thrustmaster Pedale. Letztlich sind die CH Pedale doch recht simple, antike Technik was Auflösung und den mechanischen Unterbau angeht. Ich glaub da würde ich mit den Thrustmastern, auch wenns etwas teurer würde, glücklicher werden.

also so in etwa wie das dcs-bios projekt nur eben mit MMJoy als software auf dem Arduino die die analogen Eingaben der Potis verabeitet und an den Rechner schickt? Also von der noch zusätzlich anzuschaffenden hardware wäre es mit Arduino und Usb-Kabel getan?

hrm, da fehlt jetzt nur der controller? Den müsste man nachkaufen und dann mit den potis verlöten und eine usb-Verbindung vom controller legen? Würde nur erstmal kurz die Gesamtkosten dieser Bastelie abschätzen wollen :)

the latest patch 2.0.4 contains a fix ....''Name of airfields in the radio menu corrected''. Does that mean what i hope it means?

So i have had my T.16000m for a bit over a year now and i have a bit of play in the centre prosition, about 1mm in each direction that seems not to be covered by the spring i guess. I only feel the pressure from the spring once i go past that 1mm. I have added a minimal deadzone, so its not a precision problem, but it kinda annoys me and feels a bit weird. Do you experience the same problem and if so, did anyone of you fixed that somehow? Small update on this: i have opend the stick to regrease, cut the red wire to disable the green light and check out why i have this tiny but annoying bit of play/movement around the centre. The 'gimbal' (if you want to call it that :smilewink:) is pressed against the housing top-cover by a round cup which itself has a hole at the bottom through which the wiring and hall effect sensor go. The spring presses against this cup and when the joystick is centered, this cup is supposed to touch against the housing top cover completely flat, without any play or wiggle. With my unit, this was the case, but the actual grey round gimbal (which you can see from the outside top side) had afore mentioned tiny wiggly play when the cup was in its flat cenetered position. For testing purposes i made a very flat, small ring from photo paper and placed that inside the cup. This closes the small gap between the grey gimbal and the cup which almost completely eliminates the centre play. As a permanent solution, i'll probably sand about half a mm off the cup (though one has to somehow free that cup, probably unsoldering the wires for that). And what do you know. Before, it was mostly this annoying feeling that the stick would always rock a bit before i felt the spring providing pressure against my movement. And i actually had to add a small deadzone of 7 in the centre position in target because every now and then it would not centre completely. Both, the wiggly feeling and the dead zone requirement are gone...good bye target for the time being. When i make that little tweak permament i make some fotos and post em here.

hrm, i actually thought he could control the aircraft despite superimposing the pdf. I just gave it a try in borderless mode as you suggested. You cannot control the aircraft of course, but track ir still translates head movements. I guess that why i thought Bunyap had a special trick to be in control of both simultaneously. I guess all the hussle with kneeboard builder would not be necessary if it was somehow possible. Anyway, i think this works quite nice. Autopilot is my new best friend i recon.

thx a lot guys. This gives me more than enough to take a good look at this module. Actually, my brother and i are thinking about getting it. Since they added multicrew in august, this has become a very interesting aircraft.

Hey, i am interested in the Gazelle and would like to read a bit in the Polychop manual for that module before i decide whether to get it or not. I didn't find anything on the forums (Chuck's excellent guide of course). Anyplace to download it?

just for clarity. If i forget to disable my mods before an update to dcs world, all mod files that this update touches are moved to the ingame '_000backup' folders. The easiest/safest way should then be to simply open OvGME and disable and then reanble all mods, which then should be copied over from my root mod folder, right?

OvGME does not use symbolic links to keep the original dcs folder completely untouched, right? Nexus mod manager for instance works with symbolic links and Mod Organizer for the Bethesda games presents mods via symbolic links to the orginal game folder only while Mod Organizer is running. Do i have to disable all mods before i apply ab update for DCS World like we needed to do with JSGME?

@Codawa...na da bin ich ja mal gespannt. Wäre ja klasse wenn endlich mal einer nen metallenen gimbal mod der in die Warthogbasis passt fertig kriegt. Wie ist das eigentlich mit den Sensoren? Klebst du die dann einfach unmodifiziert drinnen fest, muss da softwareseitig was geändernt werden?

Hey, during the F-15c red flag series, you sometimes displayed the mission briefings/charts/maps in your pdf reader directly ingame, apparently being able to look around the cockpit with head tracking and manipulating the pdf with your mouse simultaneously. I think thats really useful (more so than the kneeboard) to learn a new module. Having the entire A-10c manual pop up in the cockpit with the press of a button and jumping to whatever section your are working on, i mean. Would you be so kind to let us know how you managed that magical feat?

noooooooooooooooo,...alright, np. I guess i'll look into a new graphics cards when vega hits in 2017.

My 7870 2gb works alright with 2.0 when it comes to raw rendering power, vram is another issue. It reuns pretty well with medium textures and i think it looks nice enough. But i have a bit of a gripe with the cockpit textures at medium texture level. When i set textures to high, a get a bit of lag in the Vegas area, hence this is not really working for me. Is there any way i can set cockpit textures to high but leave all the other textures at medium? I did not find a cockpit specific texture value in the config at C:\Users\...\Saved Games\DCS.openalpha\Config\options.lua Any place else i can change that?

@Ciribob ...just wanted to give my thx to you for your continously hard work and a really great addition to the dcs experience. My brother and me updated to the lastest version yesterday and played on the VSaaf server. Their srs ip is the same as their dcs server ip...putting that into srs was a piece of cake and boom, we were connected and everything was working fine. Actually, now i think its really great to have srs running as a standlone/seperate program from ts. Whatever might happen on the dcs server you are playing on...having ts running in the background with a different ptt configured as a back up keeps you in contact with your buddies if need be. I'd like to give a bit of feed back concerning some addtional features that would make the convience side of srs on par with advanced features of ts or the like: 1.) saving favourites with name and ip address 2.) in ts, you can adjust loudness per individual connected client. Some people are really loud and others are barely audbile. This function allows you to boost or dampen individual players. This would require a list of all connected players within srs of course. I am no programmer or coder so i don't know whether my next question is an issue at all. Are there any security concerns around srs in the sense that someone might get access to my computer when i connect to a server or someone connects to my srs server running from my main pc? Use srs as a backdoor so to speak? Did you take any steps to ensure this can't happen? Please don't take offence about the last question. I install most programs without thinking about that sort of thing very much. I just thought its always good to address this issue in this day and age.

Quote: Originally Posted by sc_neo Hey, i set up SRS yesterday and it looks quite the neat program. Today i noticed that the distinct transmission 'click' when pressing/releasing the ptt button is not audbile on most/all radios. I can hear it in the L-39 (only one radio), in the first AM G radio of the F-15 but not the other two radios, and in neither radio in the A-10c and SU-25T for instance. Any reason behind that or is something wrong with my installation? By the way, i have addionally installed and set up the the 'auto connect promt' file on own pc from which i runs the server and dcs 1.5/2.0. I don't seem to get the auto connect promt myself. Does it work for external client connections only or should i get the promt as well if i forget to connect to my own server when i load up a dcs mission? It sounds like you haven't actually turned on the mic click effects. Have a look under settings and turn them on (Tx/Rx Effects). The Mic click you're hearing in the L-39 is probably the actual in cockpit one from the module. @Ciribob ....nah, that wasn't it. I had turned those effects on all along....what i failed to do, was to turn up the volume for the 2nd/3rd radio though, silly me, i know. Anyway, works like i should now. Thx for the support. Hope to put SRS through its paces this weekend with my brother.

ok, i play around with it a little bit. Atm i mainly play on NTTR, i guess it makes sense to wait until 2.5 is out for a couple of weeks and all the menu stuff is finalized before investing time into the needed mods. Thx for your help and hard work.

Hey, i set up SRS yesterday and it looks quite the neat program. Today i noticed that the distinct transmission 'click' when pressing/releasing the ptt button is not audbile on most/all radios. I can hear it in the L-39 (only one radio), in the first AM G radio of the F-15 but not the other two radios, and in neither radio in the A-10c and SU-25T for instance. Any reason behind that or is something wrong with my installation? By the way, i have addionally installed and set up the the 'auto connect promt' file on own pc from which i runs the server and dcs 1.5/2.0. I don't seem to get the auto connect promt myself. Does it work for external client connections only or should i get the promt as well if i forget to connect to my own server when i load up a dcs mission?

So i have set up Vaicom yesterday and it works pretty well with 1.5, although i guess i still have to train win 7's voice recognition a bit further. Thank you very much, i have taken a look into the VA command list....and this stuff looks pretty advanced and comprehensive. Now, as stated in the manual and in the opening post, 2.0 is another story. Whats the current state of Vaicom 2.0 and NTTR? I have a couple of questions towards the limitations of Vaicom and the Nevada map. 1.) Installing ''VAC_ATC_Menu_Mod_and_MacroBuilder-v1.1'' into DCS World 2 OpenAlpha does more harm than good and messes the radio menu up, right? 2.) For 1.5 i manually have to edit the VAICOM_fetch_data.cmd in Voice Attack and alter this line ''COPY /Y %USERPROFILE%\AppData\Local\Temp\DCS.openbeta\tempMission.miz TEMP\tempMission.zip'' so it works with the 1.5 openbeta. Do i have to change that line so it reads openalpha instead of beta? It seems to fetch the data alright in NTTR even when i leave that line ...\Temp\DCS.openbeta... 3.) Is the ATC communication the only problematic thing, or is everything affected? Coms with my wing, Jtac and Awacs seem to be working, right? This can be absolutely incredible...especially the coms with the flight wing...