JLX

I've had mine for a few weeks now and they are fantastic! Not only are they smooth and precise, but they are also very compact and silent. While expensive, they're extremely well built and the vertical movement is perfect for us desk jockeys without a sim pit. I fly helicopters 98% of the time to which they are particularly well suited. For toe brakes, I have programmed my CH Throttle to add two virtual slider axis (for the toe brakes) to my controller. I activate these with the thumb-joystick, when I pull back they apply the toe brakes evenly between left and right. When I push the stick forward, and slide it left or right, it applies differential braking for planes without nose-wheel steering. If you happen to be using a CH HOTAS and are comfortable using the CH Control Manager, I've included just the toe brake portion of my script below. You'll need to assign CMS.A1 and CMS.A2 to Slider 0 and Slider 1 on the CMS Controls tab and then (when running the HOTAS in mapped mode) you'll see the extra two sliders appear in DCS and you can assign these new axis to the toe brakes. The regular thumbstick axis still behave as usual so you can still use them for slewing/etc. If you don't use CH Products, I'm guessing that you can do something similar with TARGET or whatever Saitek/etc. uses. Hpoe that helps. // // Make Thumbstick into Toe Brakes: // AFT = Even Brakes // FWD = Differential Brakes // %define Midpoint 128 %define UpDownDeadzone 16 // tweaked for the play in my particular stick %define FwdAftDeadzone 12 // adjust as needed. %define IsAft [JS2.A1 < (Midpoint - FwdAftDeadzone)] %define IsFwd [JS2.A1 > (Midpoint + FwdAftDeadzone)] %define IsUp [JS2.A2 < (Midpoint - UpDownDeadzone)] %define IsDown [JS2.A2 > (Midpoint + UpDownDeadzone)] %define AmtAft ((128-JS2.A1)*2) %define AmtFwd ((JS2.A1-128)*2) %define AmtUp ((128-JS2.A2)*2) %define AmtDown ((JS2.A2-128)*2) %define LeftBrake CMS.A1 %define RightBrake CMS.A2 If (IsAft) Then // Brake Evenly LeftBrake = AmtAft; RightBrake = AmtAft; Else If (IsFwd) Then If (IsUp) Then // Reduce Left Brake LeftBrake = AmtFwd; RightBrake = AmtFwd - AmtUp; Else If (IsDown) Then // Reduce Right Brake LeftBrake = AmtFwd - AmtDown; RightBrake = AmtFwd; Else // Brake Evenly LeftBrake = AmtFwd; RightBrake = AmtFwd; EndIf EndIf Else // Release Brakes LeftBrake = 0; RightBrake = 0; EndIf EndIf

Hi, I was just testing your Radio-Comms script for VoiceAttack and ran into the issue where DCS is not recognizing the commands as you mentioned in point #2 (although VoiceAttack recognition & verbal confirmation are working correctly) As VoiceAttack is up to date and my own profiles are working fine, I dug into your demo script and found the problem: You're sending the KeyPress commands with the "Standard" input method instead of the "Windows Game (DirectX)" method. Here's a screenshot of what I'm talking about. I adjusted your demo script to fix this and it works fine now. Also, VoiceAttack doesn't need to be run as Admin. I was planning on writing a similar script for radio control but as it's tedious I never got around to it. You've done a nice job and I'd be happy to give you a few bucks for your efforts. Also, I don't know if you've only done this for the demo, but shorter command strings would be nice. Words like "radio" and "tower" are already implied and could be thought of as default. Also VHF could be AM/FM/etc. So, rather than "Tune VHF Radio to Batumi Tower", perhaps consider something a little more terse like: "Tune FM to 123" or "Tune AM to Batumi", "Tune ADF to 477" Food for thought and thanks for a very useful VA profile! It would be nice to see this for other modules <cough>Mi-8</cough> too! Cheers.

Crikey, no wonder I couldn't find it! Tnx.

Title pretty much says it all. I've got all 6 red light brightness rheostats maxed yet 3 gauges aren't illuminated at all. Bug?

That makes sense. I'm just encouraged that you are interested in expanding to other modules. As mentioned, I fly mainly helos (Huey & Mi-8) and would be happy to help if/when the time comes if you'd find that beneficial. Sent from my tablet using Tapatalk.

Wow. Just found this thread. As I play DCS solo, this is most welcome! I am often looking for more things to do. Thank you for sharing your efforts. I'm eager to check out these missions once I'm back home after the weekend. The generated kneeboard pages are a wonderful addition! I find the kneeboard an excellent and immersive tool that is often under used. Without even having tried a single one of your F-86 missions yet, I'm already wondering about the potential for expanding your tool for other modules - especially helicopters. Apart from my personal preferance for rotorcraft, helicopters would benefit from a wider range of mission types that cannot be auto-generated at the moment. Things like cargo pickup/delivery, SAR with radio tracking, recon (perhaps marking targets with smoke), etc. Regardless, more missions for us single players makes the DCS experience much more rewarding! When you make your own and therefore know in advance what you need to do, immersion is lost. Thanks again. Sent from my LG-V497 using Tapatalk

I've been meaning to chime in on this thread for a while and a little surprised it hasn't got more replies/attention. I'm also running a solid system (3570K w/ 16G + 1070) and get 85-90FPS over the Nevada strip with literally everything maxed at 1440p. However, with the Vive (using the VR preset and ground clutter/trees reduced to 0 as well as turning off all shadows) 45FPS is the absolute max I can get with dips to 30 !?!! Considering that the Vive is rendering 2160x1200 (1080x1200 per eye) it's pushing 2.6 million pixels and struggling to maintain 45 FPS. At 1440p you need to push 3.7 million (40% more!) yet the framerate is double the Vive with way more eye-candy as well! I do realize that for VR you aren't just increasing the pixels rendered from a single camera and have to render 2 scenes for each eye. While this requires additional overhead, I'm surprised just how much performance is lost! Also, it seems the Vive is locked to stepped values of 30/45/90FPS and I don't yet understand why that is. I'm hoping that I'm actually pushing something like 80FPS and the Vive is "rounding down" to 45 and future optimization will unlock more of it's potential. I'm enjoying many different VR titles and also believe the Vive to be superior at present with it's tracking system and hand controllers (and lack of exclusives). However, the VR title I'm MOST interested in is DCS. At present I share the OP's frustration and while I recognize that VR implementation is still in beta, I hope Vive performance can be significantly improved in the not to distant future. I'd also welcome any additional information about this that I might have missed. Thanks!

Wonderful suggestion! +1 From me too. Sent from my LG-V497 using Tapatalk

That's a fair point. Those users would have every right to be upset. Even offering them a discount on a paid Caucasus 2.0 map would be unlikely to appease them. I was just trying to think of a way to leverage the training nature of both the map and trainor aircraft to those that might gain the most benefit from them, including ED. Sent from my LG-V497 using Tapatalk

I've paid for Nevada too. But, as you can see, I was also suggesting that the Caucasus map (and Su-25T) become a PAID product and existing Nevada owners would get the new paid Caucasus 2.0 for free as they'd have already "pre-paid" so-to-speak via their Nevada purchase. Personally, that wouldn't bother me as I would have paid for one map and got the other included by default. If they were to switch which one was free and which one was paid I'd still have both for the same price as I originally paid and new users would only have the one free map just as before. I can't see why that would be irritating. But, that's just me. Anyway, I tend to agree in that I don't realistically think this will happpen. However, from my point of view I still think would be good idea moving forward for DCS. Both as a base introduction for new users and also to encourage training missions like the "A-10C Basic Flight Training Campaign" to be made for a globally available Nevada map instead of a specific theatre. Regardless, I'm just stoked that the Caucusas map is getting an upgrade. Beyond that, all this is just musings and conjecture. Cheers.

Feel free to move it to a new topic if that's more appropriate Skate. I think it's a suggestion that's worth ED considering even if they decide against it. Tnx.

I agree but I'd go further: I'd make Nevada the FREE map! We've already established that new users need a good first impression. Well, Nevada incorporates all the new tech and looks amazing! What are new users doing? Well... they're TESTING and TRAINING.... Hmm... Sound familiar? Why not let Nevada do exactly what it's designed for? Give them two training aircraft, the TF-51 and L-39 on the Nevada Test & Training Range for free. Then when they're ready for combat, they'll need to purchase new modules and theaters. But what about those of us that have already paid for Nevada? This is where I'd suggest that an updated and expanded Caucasus map (ideally that would include the Crimean Peninsula so we can model more current scenarios) become a PAID terrain. Everyone who has bought Nevada would get this Caucuses 2.0 map for free. So, we'd still have both terrains while having paid for only one. I would also release the updated (but not yet expanded) Caucasus map when it is ready and simply call it "early access" (or whatever) so as not to delay us from enjoying it while any possible expansion is developed. A big change like this makes DCS 2.5 a good time to do this. Caucasus missions are likely going to need to be updated anyway. So make the big changes all at once. Lastly, I'd update the SU-25T to a full DCS level product to mirror the A-10C. FC3 has the lower tech Su-25 and A-10A but both would then have improved versions as DCS quality upgrade modules. This makes a lot of sense (to me anyway) and also leverages existing work (Caucasus map, SU-25T) that could use an update anyway (and in the process becoming paid) while also showcasing the latest and prettiest (Nevada, L-39) that ED has to show right now. Hopefully, it would also encourage mission designers to make training missions for Nevada (as that's what new users who need the most training will have) and combat mission for other theaters. Anyway, just my $0.02 as always.

That's a good point. But, even if it does break missions, I'm still really excited and glad theatre dong it anyway. Updated maps are more important that backwards compatibility. While a bit of a pain, missions can be updated/rewritten if necessary. Sent from my LG-V497 using Tapatalk

+1 I've run into this too and as a HOTAS lover (and VR user) it's really important to have complete and flexible control maps. I'd go further as wish that there were options for both toggling/cycling switches on/off as well as setting them up/down. It may sound like a low priority nit-picky request, but it makes a big difference in useability and consistency between modules. Complete and flexible key binding deserves as much attention to detail as the rest of the module. Sent from my LG-V497 using Tapatalk

I've got a couple of questions about lights in the Gazelle: Is the "Console Lighting Rotator" working as intended? When I rotate it I expected the blue highlights around the controls to change intensity but it doesn't seem to do anything. I find the blue glow too bright and want to turn it down. EDIT: Figured out how to turn this down with the UV Lighting. What does the VARIO mode of the Landing Lights do? How does this work exactly. Thanks.

I use CH gear which has very strong programability. However, I find assigning controllers directly within DCS to be faster and more practical for a few reasons: * The ability and management of layer modifiers and toggles is well done and something I use a LOT. This can of course be scripted in 3rd party configuration programs but is generally more cumbersome. * As modules get updated, bindable functions also change on occasion (if rarely) and are easier to keep track of in DCS. However, there are a few things you cannot do without 3rd party software: * You cannot assign key functions to axis to turn a mini joystick into a hat switch for instance. * You cannot assign arbitrary keys to HOTAS switches, you assign DCS functions. This may seem like a pointless distinction, but you can't say assign F1-F12 to buttons within DCS to operate the radio menu options for example. For me, the advantages outweigh the disadvantages and I much prefer the convenience of sticking in DCS. That said, I recommend you check out Voice Attack and use that in conjunction with your HOTAS for an extremely flexible setup. Sent from my LG-V497 using Tapatalk

The Huey is my favourite module. What I want most is to have more things to do with it! In particular to shuttle people around and see them visually represented in the back. How cool would it be to look over your shoulder and see 3 guys next to the gunner waiting to get dropped off and a medic tending to a guy in a stretcher? I know the following isn't likely to get implemented but hey, this is a wishlist ;-) See who and how many you're carrying in the back (troops? wounded? supplies?) Be able to line drop troops while hovering Be able to pickup wounded via hoist/basket (perhaps operated by a medic up top?) Embark/disembark animations Here's hoping!

Just wanted to add my thanks for great info! The fact that you cannot see the entire contents of the HUD when your head is in a normal position seems like an obvious bug - no? As other's have also pointed out, in order to get the proper field of view required, you're head position has to be moved WAY forward from it's normal spot on the headrest. The contents of the HUD are not visible with my head on the headrest in a "normal" position: In order to fully see the contents of the HUD: ...I have to move my head forward and sit like granny with her chin on the steering wheel: I use close-up snap views as a workaround when I want to read the HUD. However, it would be really nice if ED it got sorted for 2.5 as it's really important for VR! Does anyone know if this is an acknowledged issue? Is ED even aware of this?

I know this is a necro thread but figured I'd revive it rather than start a new one. I've just tried The Bay of Hogs first mission and my monitor literally blacks out at the 5th waypoint when the bridge has been marked with red smoke. I figured this was just a glitch in my system (I just put in a new 1070) and tried it again today. Exactly the same things at exactly the same point in the mission. This can't be a random glitch. Perhaps something in the mission scripting is triggering a DCS bug? I have no idea but figured it post in hopes someone else might have some insight. My monitor literally goes black and shuts off until I crash (I can hear it) and then it pops on again. Super weird I know but it is what it is. BTW, all mission triggers and success messages worked just fine until that point. The last thing I heard was the doors opening and the smoke being fired. I saw the red smoke on the center of the bridge just before lights out. I don't have time to fly it again right now but I'll give it a 3rd shot another day see if I can get any more info. If anyone can help with this - please do. Thanks! EDIT: Ok, I'm an idiot. What was happening is that my screensaver was kicking in! I guess I flew that mission very efficiently so that I'd arrive at the bridge at exactly the same moment. Crikey. That was a weird one. Looks like in Win10 (prob after many complaints) the joystick doesn't prevent the screensaver from coming on anymore. As I use a HOTAS and Voice Attack, I don't touch the keyboard or mouse. Well... problem solved anyway.

No, I'm talking about being able to bookmark specific pages so you can quickly jump to them: If you look in the Kneeboard section of the control customization (of most Belsimtek modules - MiG-15, F-86, Mi-8MVT2 all have it) you'll see you can assign shortcuts for the bookmark functions. Edit: I just found your Nav Kneeboard pages. They're another good example of why bookmarks are so great. You can quickly jump to reference information like this, then jump back to the map, or the weapons stats page, or some other reference without flipping like crazy hunting for what you're looking for.

I love the bookmark feature of the kneeboard! It makes using it so much easier! And when you start adding in all sorts of additional information, bookmarking becomes essential! Not only would I love to see bookmarks added to the Huey - I'd love to see this as a standard feature on ALL DCS modules! If anyone at Belsimtek reads this: Will the bookmarks that are in other Belsimtek modules come to the Huey? Is this feature something that you feel you could convince (and would want) ED to adopt? Or, is it something that you'd prefer to keep as a Belsimtek exclusive "perk"? If not adopted universally, is it possible (and would you be willing) to put it out as a mod that we could use with other aircraft? I just find it so damn useful that it's to the point I find it irritating when using a module that doesn't incorporate it. Thanks in advance for any/all info. Cheers!

There seem to be two schools of thought about what Combined Arms "should" be: - Move in the Steel Beasts direction and grow to be a proper ground unit simulator or; - A commander/JTAC style RTS with an improved tactical interface. I believe CA has huge potential but right now it is in the middle ground doing neither job particularly well (yet). Personally, I am strongly in favour of a fleshed out commander/JTAC role. I would go so far as to suggest that any manual control of units beyond observing/marking a target is unnecessary. Directing units should be via command, not direct control. IMHO, the view from a ground unit should serve a similar function as the existing F6 released weapon view. Collectively, the entire combined force is your "vehicle" and each unit merely a weapon on that "vehicle". As pilots, we don't take control of our weapons and manually "drive" them to the target, we leave that to the guidance system. Each non-CA player (or AI) is the "guidance system" of their aircraft; "fired", as it were, by the commander. If you're the commander, BE the commander. Don't micro manage. That would be my design philosophy anyway. With the exception of spotting/designating targets all the CA action should take place on the tactical map. If ED wants to move into DCS-level ground unit simulation, fair enough. But leave that for specific modules like the aircraft. Ironically, even as arcadey as Battlefield is, it's commander mode doesn't let you jump into first person, it focuses solely on high-level tactics. I believe Combined Arms should be similar except with the depth that we've come to expect from DCS. My advice: Adopt a purely strategic/tactical design for Combined Arms and stick with it. Don't water down the experience with a light/arcade FPS mode thrown in the mix. Save the first person experience for full DCS quality sim modules. As always, just my 2¢

Bumping up the Pixel Density with the slider didn't make much difference on my Vive as you suggested. However, I can't locate the VRSetting file you mentioned. Can you please give the exact path? I'm running the non-Steam version but searching for "vrsetting*.*" in the DCS directories and the Steam directories didn't find anything. Tnx.

Smart to wait if you can. If you're not an early adopter, probably the next sweet spot for upgrades is after VR, Vega & DCS 2.x have all had time to mature a bit and drop in price. For me, I've already paid a premium to get the Vive and without a decent GPU I'm not making the most of it. There is definitely a cost to jumping in early but it's also exciting to experience VR in it's infancy. Warts and all. :-)

My MSI 1070 is enroute as well to replace my aging 7950. Must admit that I bought it out of frustration as I don't like Nvidia's proprietary Gameworks/GSync/etc. but I want more oomph than Polaris, and Vega is still to long a wait. While I may not like their marketing tactics, there is no denying the green team makes some speedy GPUs and (according to the 2016 Hardware Benchmark thread) DCS still seems more Nvidia friendly at this point although I really hope things will even out in the future. Regardless, I'm looking forward to seeing how smooth I'm able to get DCS running in VR (Vive). Fingers crossed!