TopoSolitario

Yo uso una con 15 botonoes y 3 diales... meto ahí principalmente las teclas de función de la radio, el piernógrafo, opciones adicionales de las naves (admite 3 perfiles así que tengo una para teclas especiales del huey, del apache y del kiowa, que es lo que más vuelo) y paso páginas del piernógrafo con el dial grande... no se si costó 22€ en aliexpress y hace su función al 200% Para VR además le he puesto recortes redondos de espuma que me ayudan a identificar al tacto las teclas, para no pulsar lo que no debo... te acostumbras a usarlo muy rápido y funciona de pelotas. null

Hello @MBot! I've been working on some changes on your Artillery Scrpit (a really great tool!) to adapt it to our needs, basically it started as a small change to add voices to the script for the Artillery Command to acknowledge instructions, but it evolved with lots of changes plus a side-script to create markers directly from the radio menu (I don't like F10 map and sometimes in VR it's even suicidal to open it as it can quickly degrade performance). I'm contacting to say "thank you for the original script"! and to comment some of problems with it that I solved that yo can tweak too: Compatibility problems with other scripts: Menu options are managed with names and not node pointers, that is causing with other custom scripts to remove radio entrances... using nodes instead of names solves the problem, but forces to work on all root nodes and a way to clear them without clearing the main one (if yo remove and rebuild the main node it will go down the F10 menu options list). Performance wise upgrades: Some processes are consuming unnecessary resources, as example, to pick new FO units birth you're scheduling a function that keeps running forever, it's much more light to listen to unit creation event. MGRS grids available in 100km not properly pooled: This problem is important as not all grids are 100x100km, so if you find what is 100km east you can jump over a smaller grid and make it impossible to pick a point there using only the Radio menu. To solve this I'm using only 25km (actually it's as far as you can "see" using a kiowa MMS) and pool increments of 1 kilometer to find all grids on that points. This is working perfectly, 25km is a parameter so it can be adjusted to whatever you need for your mission. Additionally I added some configurations for my changes, that is, being able to set the radio frequencies Command is using for artillery strikes, so you can set it up on your mission, then even no-FO units can sintonize and hear what is going on with artillery support. And, as I get voice feedback for all operations, I can choose whether to have text messages from FO only, FS only, All or None; this keeps the balance between inmersion and information. You can see it working here, jump to 8:15 for a direct show of using artillery script with voices (yes, everything is in spanish) Again, thank you very much for your original work!.

The monocular is terrible. Even worse than the Apache’s IHADSS — you see it as if it were just a handspan away from your face, with perfect resolution and focus (I wish I could see that clearly up close). It feels more like having a metal disc the size of a CD stuck away from your helmet than an actual monocular fitted to the eye. The Ka-50’s one looks infinitely better (and it’s basically the same thing). It’s missing configuration options: you can disable it, but then you just get the yellow circle floating in empty space. And if you remove it, you also lose the top part of the helmet that adds immersion (the two tracking pivots). I think an additional option is needed to blur it — maybe in LUA you can tweak the position or transparency so it looks more realistic. Something will surely come out, but now keeping the monocular visible in VR is terrible and distracting (the opposite of the intended use)

Found this post trying to report the same issue, I agree with average_pilot, it seems like the visor is rendered with light and reflections coming from sides and behind, where helmet and your head is, and light should not come from that directions. I mean, like if it is rendered as a floating object not taking into account your head and helmet. It is inmmersive and usable, but in fact it does less good than bad about vision quality

It is cool BUT it seems it renders lights and reflections like if you have no head, with light coming from sides and back causing really weird effects that should not happen with a visor attached to your fade.

June 2025 and this bug seems to be still unrepaired. Maybe the Type071 is not the most used ship in the game, but we are using it to simulate other ships that are not present in the game and have similar capabilities. We were testing it yesterday and all units spawn in position 01, so two helicopters implode when spawning at the same time.

Is this going to be the next helicopter in the line that DCS is goint to announce at some point soon?

Hi there, I've created this mod for the Ursa Minor to be used as Collective. The space version seems to be great but it is turned 90º and not really usabe for a HOCAS setup instead of a HOSAS or HOTAS setup. So this mod places it properly for this use. You can get it here in thingiverse: https://www.thingiverse.com/thing:6849517 Things to note: Mod is not destructive: which means that no damage will be caused to the stick. In fact, official Space Combat version uses a pretty similar extension but perpendicular and not longitudinal, which is great for HOSAS setups but not too great for a HOCAS Use JST Mirco 1,25mm 3PIN 200mm extension: I used a cable extension (easy to find and cheap) male-female that goes inside the part, this way you can dismantle and go back to the original stick. It is much better than cutting the original cable. Will need some additional screws: 2mm x 10mm computer screws could be used to attach the extension to the base, re-use the original screws to attach the stick to the extension. Use little to no supports: Extension is in two parts, you don't need supports (as long as your printer can cope with 25mm bridges), so it's fast and easy to print and install. You can see a prototype quick video here: https://www.youtube.com/watch?v=US7yK1rpK0M I hope you find it usefull. I'm using it on DCS and the only drawback is that even with fully pressed dampeners in the base, the stick still goes a little forward if you are 20% or below, but if you are flying over 1/3 power it will remain in place as it is fairly balanced. I'm testing it as much as I can with the UH1 (using the AWESOME mission "I love this job" now in version 4.0 updated to latest map changes) and the Apache, where having so much buttons and sticks makes it perfect for VR as you have almost everything without modifiers and having all tue UI, kneeboard and NVG stuff in the base buttons. And it is working amazingly well... the only drawback is the 30º movement range, but once you get used to it it works perfect.

I'm using Antimicrox too... after some testing this is THE ONE. It is easy to configure and works for what I need, that is, being able to use the triggers as buttons. My motherboard has integrated bluetooth and wifi, so I'm using it (both for the macro keyboards and controller and wifi for airlink on Oculus Quest). I find no latency using it as it's intended for gaming. Depending on the dongle you're using for BT you can find some latency (that's pretty bad for the ManTrack), if you find latency it's the dongle not the gaming controller. I have to give a second thought for the mappings as I've some functions I need and don't have. But it already is closte to IRL buttons and hats locations and if I need additional stuff I can map other buttons in the center macro keyboard. I use the macro for TV/FLIR, IAT and George without modifers. As I'm on VR I find pretty useful to add some haptic feedback on the buttons, just attaching some adhesive foam to properly find important buttons like the ones I use for Slave, Polarity and FCR Short Scan Apart from that, I find this solution not only "cheap" but great for this purpose, it may not be a complete TEDAC true to live, but... 50€! Transition between pilot and gunner is much easier as you have different controls with different functions and different muscle memories. When I only pilot (FCR and L hellfires, rockets and gun, without using TADS) I don't use it... if not, switching to the CPG position feels pretty natural, and if I have to take control when George insist on crashing (happens a lot if overloaded) I even don't have to abandon the CPG spot, just change controls, grab the stick and keep flying. How is your experience going with it?

As I'm using VR, I created some custom caps to have a better haptic feedback when "searching" for the right button. Grey ones mimic some buttons of the TEDAC unit on top the TAD/FCR/PNV on the right, top ones are for TV/FLIR Bottom one is the IAT (can't push it into the left controller, too much needed buttons there) Black ones are dedicated to George Four arrows with small protuberances to locate quickly each one top left for show/hide George interface top right for take and release flying controls That way my fingers in VR has something to "remember", and it works like a charm!

Oh! you got big bucks invested there! I think you can add an attachment between the MFDs, the best position for me for the TEDAC QUEEN is over the stick at the same depth (that should be about 15cm away from your table). Not 100% accurate but the feeling in VR is much more inmersive than just grabbing it on your legs or something. If you went for the exact same controller and keyboard as mine, I can upload the STL for the attachment I'm using.

Having many more buttons and knobs between the left and right handgrips is really usefull. I see you're using an X56, I ditched the stick in favor of a much more expensive VKG Gunfighter, but I used the X56 successfully with the UH1 using this mod: https://www.thingiverse.com/thing:6660045 You get a dead stick (not exactly how a helicopter cyclic works, but much better than using the X56 as is, even with the softest spring)... forgetting about trimming is a paradise (lost)

I'm using it for VR, but you can surely add an screen for TEDAC using Helios, there are how-to's in youtube. I think it depends on the Tablet you're using, if it is capable of be used as additional PC monitor... if so, I'm pretty sure it's doable (never tried tho!) Using a bluetooth keyboard is mainly to have the LEV GAIN knobs, I move them a lot!

So, this is my desktop setup with the TEDAC QUEEN (not the king, but a nice poorman solution). I Can't afford the space needed for a simpit, I need everything to be removable and ready for storage in one minute... In VR yo uactually don't see how simple is everything, but in fact, with the new TEDAC, the Gunfighter IV, pedals, additional macro keyboard (for radio and kneepad) and still using the old X56 Thrust... well I can play VR with full inmersion!

I'll try to help a bit with that: Controller is a D9 gaming pad, it cost me about 35€ in Aliexpress but surely price and availability depends on your country. This controller has a very nice feature as it can hold a phone or a table with a spring loaded mechanism in the middle, which makes it perfect for attaching any size of keyboard, or even a screen or a device showing a screen (if you are not playing VR and want to have the TADS in there, not my case). Another good thing is that it is bluetooth or cable, if you go for cable it emulates Playstation controller and you don't have to worry about mapping the triggers. Via bluetooth it works like a XBOX controller and triggers are AXIS not BUTTONS. After a couple of hours playing, the controller is good stuff, sticks are sensitive and precise, working with the Linear tracking works amazingly well (you can add a little curve to have better fine adjustment) I'm using the left trigger for "Left Control" modifier, which doubles the buttons, and the right trigger as 2nd detent Laser (mapped to L key on keyboard") To map this two axis to buttons I'm using ANTIMICROX, which is pretty easy to configure for this purpose, and works with Bluetooth controllers. Joystick Gremlin doesn't work properly, interprets the two triggers as a single axis and you need to keep screen in focus or otherwise it stops sending data to vjoy. AntiMicroX doesn't need other software like Vjoy. Keypad is a bluetooth macro keyboard, this one cost me about 20€ in Aliexpress I searched for a Black one (others I use are transparent acrilic) and I wanted it to have only 2 knobs to mimic Gain and Lev adjustment... which are a must operating the TEDAC Number of buttons are not important, this one have 12, whic I mapped 6 to control George, 3 for the top buttons and the other 3 to add functions like TV-Flir change. But all in all I find it to have enough buttons leaving aside only some minor functions. For mounting to the table I'm using a custom 3D printed attachment, I tested a first version yesterday but it was too far away and I put my face into the TADS monitor, so I'm printing this one right now which will be on top of the Gunfighter stick, perfect to grab at any moment and usable when in pilot position to control George and other secondary buttons (like Night vision adjustment) After a about 4 of hours getting the hand of it, having a separate controller for the TEDAC is a must have for any pilot. A custom TEDAC unit is too expensive (and too specific for the apache), so a cheap solution than can still have great usage is mandatory, and I really think this combination does the trick with A+ results.