Wazoo

I gotta say... I was not expecting too much. But now? I can't *imagine* flying DCS without it.... or ED. X-Plane 11 is fantastic VFR.... however... as a real world IFR student, I don't use VR as I need to reference charts and heavily work the GPS for navigation.

For what it's worth, tracking while simming has been an absolute non-issue for me. ED dogfights with my head cranked as far as it will go behind me has been no problem at all. For room scale, I have about a 7x7 foot area mapped out and also, very rarely lose positional tracking. Crushing RoboRecall, loved Rick & Morty, and suck at but love Space Pirate Trainer. Only real tracking issue I've found is if my controllers stay behind my back for an extended period of time or sometimes if they are too low. But honestly, for the same visual quality of a Vive Pro, and *especially* for simming (Project Cars 2 in my 6DOF motion platform is f**king nuts!), this product at $399 is hard to beat.

I never owned a Rift or Vive... but all I can say is I'm REALLY impressed with the Samsung. I've been sucked into Elite Dangerous of late as the feeling of flying a spaceship is incredible. I've also flown around Nellis in the A-10 and I had to pick my jaw off the ground. MFD's are readable (although better when using VR zoom) and the feeling of flight is ridiculous. Worth an upgrade? That I can't answer. But if you *don't* yet have a VR headset, Vive Pro visuals, easy setup, no external sensors, all for $399 seems like a no-brainer to me if you are in the market for a VR headset. Now if only I could easily flip switches in the cockpit.... ;) *Edit - Oh... and as you probably know... Microcenter has a great return policy (at least the one here in Southern California). If you don't think it is worth the upgrade, you could always return it.

I picked this headset up and it is amazing for DCS. Just thought I'd let people know about the sale as I never see it for below $499.

Ok. Thanks. That is helpful. I was frantically checking out MY clock positions and usually finding nothing.

When my wingman calls out clock and distance to an object (or launch), is that relative to me or him?

I believe it is LALT-Y to switch the coordinate system used in the F10 map during mission. I just wish that when you select a unit on the map, the little info window switched to UTM as well.

Funny you mention the Max PC article. I read it after I posted and thought "Damn! Why didn't I remember that?!" Doh!

Thanks!

Help! I thought I made a backup of CommandDialogsPanel.lua from the \DCS World\Scripts\UI\RadioCommandDialogPanel directory (I'm trying to center radio text on an Nvidia Surround setup) but apparently I didn't! :doh: Now I keep CTD'ing. Can someone help! Thanks!

Change CDU background color? I use iControl on an Nvidia Surround setup with the MFD's in the extreme left and right bottom corners of the outside monitors. I would like to use the CDU functionality as well, but I find that unlike the MFDs which do not let in any of the "background" (i.e. parts of the cockpit or sky depending on where my TrackIR5 is positioned), the CDU sends the background through to the iPad making it VERY hard to read. Is there a way to make the background solid behind the CDU on-screen so it mirrors to the iPad the same way? Thanks! Wazoo

So... I decided to try some tests as well. I'm using Beta 3 and loading the Weapons Training mission which starts you on the runway facing into the sun. I tried EVERYTHING.... from no SLI, to using SLI, to no AA to 16QAA, to with and without HDR, and 1024x768 as well as my native single monitor res of 1600x1200 and no matter what, I get 16-19 fps when I'm dropped in the sim. Interestingly, the SLI bar shrinks significantly when looking at the sun, but grows substantially if I turn my head away. So it seems that SLI is working, kinda. As this is an easy thing to replicate, I'm curious what others find. Wazoo

I searched, but couldn't find an answer to this... although I have a feeling it just doesnt work in multiplayer: Civilian traffic. If I see a train in my "world", my friend doesn't see it in his. I assume there is no way around this? Wazoo

So I've got the Shkval targeting down relatively well, and have decided to try to utilize the HMS. I can use the HMS to get the Skhval pointing right near my HMS target. However, I then find it necessary to use the standard Shkval slew movements and lockup button to get the TA symbol. I'm confused about how to get the HMS to go into "processing" mode as described in the manual. I *think* if I do it correctly, the targeting system will automatically lock up my HMS target without further manipulation of the "normal" Shkval locking procedures. What am I missing here?

This is an issue that has always confused me. When I installed Windows 7 Ultimate, I only created one user (me) with, what I thought to be full administrator privileges. Yet sometimes Windows tells me I need to be an administrator to do something. Confuses the crap out of me. Anyways.... I do run BS as an administrator as I had problems if I did not. I did it by setting the compatibility properties of dcs.exe to admin. That solved an issue of not even being able to launch multiplayer.

Before reading the warnings about editing Lua files, I edited FOoptions.lua with Notepad. Now I only use EditPadPro6. The file appears fine... but I guess it could be corrupt (not sure how that would present itself). Either way, would that file effect whether or not the different trim logics were being implemented? DCS is installed in /Program Files... but on my gaming drive which is E: for me. I'm pretty sure Windows 7 doesn't freak out in that situation.... but the whole Administrator thing in W7 seems a bit wacky to me... :) No other peripherals attached besides my CH HOTAS. Luckily for me, I have almost no problems with cyclic lockout using the new logic and can fly it pretty well.... although I do, at times, get lockout at very low speeds when making very small adjustments with the cyclic. Happened last night while trying to get into an auto-hover. Had to quickly cancel all trimming, which returned control, and the quickly make sure the untrimmed helo didn't crash into the hill I was hovering near. :doh: My friend, however, is another story, and he is going to reinstall into a non-C: drive directory and see if that helps.

Thanks for the info. I checked and the option is changing correctly from True to False depending on the option set in the game..... but the behavior is the same. Am I correct in my description above on how it *should* behave in the original trim logic? Oh.. and BTW... is True for the old logic or is it false?

Ok... I must be missing something here. I decided to experiment with the Central Position Trimmer Mode option by flying with it checked and then unchecked to see the difference. Whelp... I can't see ANY difference. For example, with it checked, I assume based on the discussion above that it is using the new trimmer logic. To test it, I get in cockpit, pitch the cyclic forward about 30 degrees and then trim and hold the stick in the exact same position without re-centering. As expected, I have complete cyclic lockout until I return the cyclic to center. So I exit the mission, go to options, and uncheck the box assuming this will implement the old trimmer logic. I go back into the simulator and do the exact same thing. Result: The exact same; i.e. cyclic lockout until re-center of stick. Based upon my understanding of the two different logics, the older one should allow the cyclic to continue movement even though I never re-center the stick. What am I missing here?? :joystick:

I thought so too.... but if that were true, would not switching to the original trim logic solve this problem as re-center is not part of the trimmer logic? Put another way... if using the old logic, wouldn't the cyclic respond after .5 seconds in any direction even if it was not properly re-centered?

So if I understand you correctly, checking the box in the options menu enables the NEW trimmer logic... and unchecking it enables the old. But what about the variable HelicopterTrimmerMethod? Where does that come in? He's using a pretty new CH Products HOTAS (Flightstick Pro, Pro Throttle, Pro Rudders), so I doubt it is a mechanical issue. Oddly... when cyclic lockup occurs, he cannot bank left or right nor pitch forward... but pitching *back* does work... and returns cyclic control.

I'm trying to get my Falcon 4 buddy going on BS but he's having a hell of a time with the cyclic locking up after trimming. We've gone through the whole dead-zone modifying thing, but still no joy. Basically I'm trying to isolate variables right now to see what the problem is. But first, I'd like to get him back to the old way of trimming to see if that solves the lockup problem. I am assuming that the original trim logic did not rely at all on re-centering, but strictly on time-lapse.... thus if you didn't re-center within the .5 seconds allotted, tough luck. The new "center" for you stick is where ever you are holding it after .5 seconds.... is this right?? Anyway... after reading the 1.01c Readme, it says that the HelicopterTrimmerMethod variable in the FOoptions.lua file is the one that sets the trim logic. However, even in my FOoptions.lua file, that variable does not exist. When I check the Central Position Trimmer Mode (assuming that reverts the sim to the old trimmer logic), the variable still doesn't appear in that file. Am I going about this in the correct manner?

Well.... I see Matt is working with Logitech on their issues. Has anyone at ED commented on the Saitek issue? As FF sticks are few in number, I would hope that the ED devs have at least seen the issue for themselves.

BTW - When people have posted about the "center spring", is that the external one at the base of the handle.... or is it an internal one that requires disassembly?

Am I correct in discerning from messages on the forum that the trim issue was never solved with the Saitek Cyborg Evo?

So.... for the DCS:BS newbie here.... I'm trying to decide whether I should learn the sim with my tried and true CH Products HOTAS (Fighterstick, Pro Throttle, Pro Peddles), or should I hook up my Saitek Cyborg EVO FF stick and learn using it? Wondering if mixing and matching the setups would be more headache than its worth.