-Hawkeye-

I like hearing you guys' input. Gives some insight to points of view that are not common. I would say that as flight simmers, we are not that common. Specifically, we may want or desire a big screen. From the standard point of view, if you get a bigger screen, basically that means you're supposed to view it from farther away; that would be it's main purpose, as would a higher resolution.... i.e. when he shows old standard resolutions with respect to relative size of each other. However, we don't want to move farther away; we want to be more "immersed" in our video, and see more in our basic FOV. Optimal TrackIR operation is a consideration for us; it wouldn't be optimal from a far distance. So in essence we have the potential to see pixels in the context of up close clarity, as opposed to simply a larger size, seen from a distance. Personally, right now I have no real concern that my hardware couldn't handle a 4K resolution with decent performance, if I got a new screen. However, it can't help but reduce performance from what it is right now, and the question is, for what gain? That is why I chose the "2K" screen that I have, that is larger, and also has higher refresh rates. In my own case, I think I've reached the limit in terms of size that I can see acceptably (everything is smaller with higher resolution, given the same physical size). At times, I wonder if I am seeing as much as I did before using 1080p. Honestly, I think many games like RoF are optimized for that resolution, and if you use anything else, you may not see everything as flawlessly. At least, that's my theory

All of the planes in FC seem "more compact" to me, than they do in RoF. From my point of view (non-VR), the pilot's position is somewhat forward of what it is in RoF. Therefore, when you pull back your FOV fully, you can't see as much. Not saying this is correct or incorrect....just different, and it will take some getting used to. Honestly, if I remember right, RoF started out kind of like this; then later they changed the default home view to be further back for a greater FOV. This is helpful in the game, but not necessarily as realistic or true to life. If it was me personally, I'd ask them to make it like RoF; but I can understand if they don't. Everything is a compromise in these sims, with respect to reality.

Yeah, had heard that by word-of-mouth.... Congrats on your acquisition Somebody has to combat "the bad guys", LOL Seriously, it's hard to seem "good" when you're killing folks....

Very nice! Great work! Reminds me of controls rigging (pins in holes) on those choppers. Also SCAS (Stability and Controls Augmentation System) on Bell products, and the AFCU (Automatic Flight Controls Unit) on the CH-54. Nothing was connected directly on these planes! (laughing, that is what they called these helicopters in the maintenance units I worked in). All the pilots flew "with their thumbs"....except that the test pilots didn't have a lot of respect for that. KUGW (Keep Up the Good Work)

What's this J5 $H!t ? So glad you guys are just back flying with us! Great to have you. Now, continue to have fun. S!

I don't know....sometimes it seems like bad luck, injuries....just find me. Seriously, I used to get problems with equipment that nobody else seemed to have, back when I was a technician; I'd always get "the big ones". Later, I began to realize that a lot of it was just that others didn't report or address the problems "you're the only one who's reported this" or "just you and one other site has reported this", when asking for support. In any case, I can truthfully say that I initiated national changes to the entire NAS based on problems in the system that I discovered (some things you just can't fix in the field because they're software or firmware based). What kind of luck is that?

See rest of edited post.... Sorry about that....it's all too much at one time, sometimes

Problems.....Problems!!! Nothing is easy, it seems. Once I had downloaded the current "VPC Configurator Software", and the manual that goes with it (16 pages), I was pleasantly optimistic, once I read it, that things would go OK. But it was not to be, for both hardware and software reasons. First off, once you extract the zip file and place the folders on your drive, then create a shortcut to the executable (set to run as administrator), once you run it, the first thing it is likely to say is that you need to update the firmware. The firmware update file is part of the package of software that you download, and makes the device and the software compatible. Before that, you connect your devices, and let Windows install them. That part seemed to complete OK. But when I started the software, only one device seemed to show up in the list (the throttle). So I updated the firmware according to the instructions, and that seemed to work OK. But what the software calls the device is based on what configuration file you load. Then when you start the firmware update process, it disconnects the device from Windows, and then you see "Bootloader" instead. Then you browse to the file, and load it; then you end the process. However, if you theoretically have 2 devices installed in Windows, and only one shows up in the software, are you really sure which one it is? Not really, if you're new to the software and hardware. In any case, after updating the firmware and installing the configuration file for the MT-50 Throttle, I rebooted the computer and ran the software again; again, only one device (Bootloader always shows up but doesn't count). At this point, the software said that the firmware needed to be updated (again) Really? So I did the process again....but then wondered am I updating it for the joystick now? In that case, I should load the WarBRD + MT-50 Grip file, right? NO! What happened then is that the wrong config file got installed to the current device (apparently, the throttle) and nothing worked. How to fix that? First, I had to "reset configuration file", and then SAVE that file to the device (if you just reset it and then restart the software, nothing is changed). Then in the software, the device shows up as "VPC reset device" or something like that (again, you're not really sure what it is exactly). At that point, even the Windows devices called both devices *almost* the same name, so you didn't know which was which (VPC MT-50 Joystick vs. VPC Joysyick + MT-50 grip) . So then I decided I have to be absolutely sure which device is which, so I disconnected both devices, rebooted, and then removed both devices in the "Devices and Printers" section of the Control Panel. You can't tell what they are in the Device Manager; they probably show up under "HID" (Human Interface Devices) and they aren't specified clearly there. Then I rebooted again, and after that, plugged in JUST THE JOYSTICK. Window reinstalled it, then I ran the software. Voila! A device actually showed up that I knew to be the joystick. So I updated firmware again, then installed the (this time correct) configuration file for "VPC WarBRD + MT50 Grip". After that, I went to calibrate the stick (the next step). The software senses stick movements and all you do is move each axis fully in each direction, and while doing this, the min and max values are registered; then after that, you let the stick center and then save all that data to your current config file; then you have to save the file. Or so it should work. However, another problem! The X and Y axis of the stick would register movement just fine. However, the "Z" axis (analog brake axis) would not move. Huh? Whatever, no choice but to save what I have. More on this problem later.... Now, reboot, and then plug in the throttle. Windows installed, then started software....guess what? A new device showed up! Yay! Install firmware, config file, calibrate....all seemed to work for all axis there. Now it was about 1:30 in the morning, so I figured I could at least get RoF running for Saturday's session.... I started RoF and began to push buttons. Throttle things worked, stick X and Y axis worked, but NONE of the buttons on the joystick would register in the game! What the hell? At this point I gave up for the night and went to bed. 5:25 AM, I woke up with a flash of insight. Axis on the grip doesn't work, buttons on the grip don't work....axis on the base DO work....the grip isn't connected! Why? It did seem to me that the male part of the plug really didn't go into the female half (on the base side) very far at all. But what can you do about that? You carefully align the two connectors, and then you mate them together, and tighten the hand nut. What else can you do? Perhaps....seriously....that male connector can be pulled out? Have to try it right now! Up out of bed and down to the workshop. Remove handle....needle nose pliers....holy crap, it does come out! It's all clear now! Here is what you see when you receive the stick, and then what it's like when you realize later that the connector comes out! It comes with NO instructions, folks! Base of grip, as it comes in the box: Looks just like it's made to go together that way, right? WRONG! Here's what REALLY needs to be done: So THAT was just THAT problem. Ran configurator software, ran calibration....everything works! Buttons too.... Start RoF....getting late in the morning....session in 4 hours! I can do it !....? Shower, eat something....hangover Must make functional RoF controls map first! Assign main axis, test in game....throttle axis is reversed. Have to change every plane's response settings to reverse that axis. Do that on a number of planes, but realize there just isn't enough time. Concentrate on one plane and see how it works. Uncheck "invert" on the Engine 1 throttle axis, apply, export, save, etc. Check in game. Question marks over each slider indicator in game? Altitude Throttle axis seems to work OK ("W" axis). Regular Throttle axis ("O" axis) working in corrected direction, except....when I reach about 95%, it sometimes stays, but most of the time reverts back to zero, all by itself! What the hell? Appears to be associated with the end of the axis....maybe detent buttons? Recheck cal and look at all kinds of confusing field data concerning centering, etc.,....nothing in manual even begins to touch this....release physical detent allen screws....makes no difference. All testing with DIView and inside of the config software indicates everything working normally. I change axis within the game to another axis....same result; then another axis....one that is known to work without problems elsewhere in the game. Same issue! What's wrong here....? Conflict within the game! After reversing (uncheck "invert") the "Engine 1 throttle" axis, the problem began. However, "Engines throttle axis" was NOT changed, so one was inverted, the other, NOT. Conflict! When one part was saying that is was at 100%, the other was saying that it was at ZERO! Now only about an hour before FiF session start.... Can't fix everything. Only fix the planes that are in FiF Phase B. No, too much time; only fix the Entente planes, as that is what we are flying. No! too much time....only fix the Entente scouts we'll be flying. Sopwith Dolphin....fixed. S.E.5a....fixed. Sopwith Camel....fixed. Oops! forgot Nieuport 28....fixed. Now finish mapping controls! Old controls vs. new, what's logical, what's going to work best....engine, plane, pilot head, camera....updated to new buttons. 30 minutes to pre-session Teamspeak brief. Finally, practice in "Fly Now"! 30 minutes to practice new stick hardware, flying Sopwith Dolphin, Sopwith Camel. Others will have to wait! Gratified to see that response curves work just as well with this hardware, as with old; as expected. Very nice response now, accurate, somehow different....flyable, ease of control, nice, but different! Will have to practice, but things should be stable now! Flew the session, and LIVED. Didn't get any kills, but mainly had to protect my plane and life to complete the "wreath drop" mission, which was accomplished. Did some damage to enemies, while remaining alive. Very happy!

Don't really use it in-game except maybe for some Teamspeak whisper assignments. Outside of game, it's easy for me to have my hands on either side of the throttle....in fact, the height of the throttle is perfect for a hand rest for the keyboard I can scoot the keyboard left or right if I want to, it's just sitting on top, not fixed in a specific place. Same thing as I did with my old setup. Also, because of the decreased footprint of the joystick, the mouse pad is actually bigger than my old one was, allowing more movement without picking it up and replacing it.

Controllers installed from bottom side- Tray with controllers, keyboard and mouse reinstalled. Ready for configuration!

Much sanding and many coats of polyurethane later....ready for physical mounting of components

Mapping out center of stick location (same as old). Periphery and hole saw centers marked. Holes will be cut, then a jig saw with clamped guide will do the straight cuts between them. After that, I'll also cut a square hole for the throttle. This whole business will lower the actual height by 1-1/4 inches (a little more, if you include the rubber feet the bases would sit on). At the same time, there will be nothing protruding any lower than the bottom of the keyboard tray, like before (well, maybe a 16th of an inch, to count the metal base thickness). I'll take what I can get

What's really cool is when you actually try the things he's talking about. I pretty much knew about peripheral vision, and the macular blind spot which concerns night vision; but I didn't know about the other blind spot he talks about when an eye is seeing as an individual; nor really considered the loss of color on the peripheries....or a lot of the other things he talks about. I did know a lot about the hardware evolution....being old, and an old electronics technician ....but not so much how it related to the real world. I would still like to see FPS for gaming be capable to render the absolute best that a human can see, instead of just what an average human can see; he mentions that at times (high on caffeine or cocaine ) that a human can discern up to 240 FPS. Adrenaline is pumping many times when we fly and it would be cool never to have it be a concern, once the hardware can do it without any trouble or undue load. I'm running 100 FPS on a bigger screen, and there's no time at which I ever notice any less than smooth effects, in any gaming condition that I run. If hardware in the future could all do at least 120, that would be cool.

Watch this whole thing. Contains a LOT of surprising info!

Thanks for the info! It's showing near me, didn't expect it to! I am so going to see that on the 17th!

67Y (AH-1S), LOL...to start with; then a lot of others after that The things you discover....

OMG UH-1's, AH-1's and H-53's? Geez, I can't believe anybody, even the National Guard, would still being using that stuff (I mean, I worked on that stuff). 60's and Ospreys I could see.... In any case, you're in Hawaii, why you lookin' at that

Preachin' to the choir! Now show us some Dolphin and S.E.5a.

Hope you get to stay a long time!

Pretty much figure that it will take a "Reset this computer" (i.e. same as a total reinstall) to make this go away. So far, no problems; I did back up the registry before doing anything. Of course, I haven't tried using a lot of things (RoF/BoX included) yet. Right now, I've just disabled the unknown device. I'll have to see if the new stuff works 100% without any issues.

Installed the free version of CCleaner, and scanned the registry. Many issues found, 2 related to CH Control Manager. "Fixed" them all. Rebooted and ran scan again. More issues found. "Fixed" this smaller list. Ran another registry scan; no issues found. Uninstalled unknown device in Device Manager; rebooted. Unknown Device reinstalled. So far, the only solution I have is to disable the device and leave it installed. Otherwise, I'd have to uninstall it every time after a reboot.

No; if you recommend that program or any other in particular, I could try it. The guy in Klaiber's second link tried Malwarebytes and ADW Cleaner, and said that neither found "any threats". Obviously this is not a virus or malware. If you think ccleaner or any other program might find whatever I'm missing, I'm game. This guy said that what eventually worked was to manually delete entries he found. His post was not that helpful, in that he didn't really describe exactly what he searched for and manually deleted. I actually searched for the device value shown in the above screen shot, found one which I deleted, then using "find next" found about 8 more all located in the same place; so I deleted those too. Perhaps I should have deleted the entire heading instead of just the values on the right side of the screen. There were other values in that area, about 3, which did not specify "CH Products" in the string, and instead specified something about USB....I left those alone. I feel pretty safe deleting anything that says "CH Products", but other stuff I don't want to screw up.

Yeah, I had found both of those. From the latter: "A thorough search of the registry revealed 67 (CH) entries alongside the PnP entries for the pedals. After manually deleting the erroneous entries, the system is back to normal. Also deleted the leftover entry for the CH Control Manager Software from the add/remove programs listing." I'd like to know how he did that. I just did a search for "CH" in the entire registry, and it didn't come up with anything. Also, I don't have any left over "CH Products" category in the Device Manager. It just lists a heading of "unknown devices" or some other such thing. There is also no remnant in the Programs part of the Control Panel; all references there to CH Products are gone. If I uninstall the unknown device, it does remove, and would stay OK so long as I don't reboot; but upon reboot, Windows automatically reinstalls it: Here is what shows in the Device Manager: Properties: I searched for that value in the registry, found one, and deleted it. It still continually reinstalls.

Adding 1/2 inch plywood under existing keyboard tray. Since I'm mounting from underneath, this will lower the overall installation height. Next step, once glue is dried, is to cut the holes in the tray which will house the joystick and throttle. On the solid front edge, the bottom of the finished edge is now flush with the bottom of the plywood.

Prepping for new hardware, I uninstalled my CH Control Manager software. The uninstall routine notified me that I needed to have all CH devices unplugged in order to continue, and I had already done that. After uninstall and reboot, Windows set up "unknown device", so I checked Device Manager, and uninstalled the "unknown device". Upon reboot, it just reinstalled the "unknown device". I can't get rid of this device. Apparently there is something left over in the registry. I'm not good with that but I did a search for the device ID and deleted what I found. Still, it installs the unknown device after each time I uninstall it. Any help appreciated.