AKA_Clutter

I agree. I am in the process of reprograming my TM WARTHOG for the KA-50 (used CH HOTAS for years) and that is one thing I finding out. With PointCTRL, I will have less things on the stick. Will always have the stick and throttle function, but if it is a clickable button, then I plan on using Point CTRL. I also realized that this means I will have to know the cockpit much better and the systems as well. I used to have certain buttons to do the main ABRIS functions and that was OK. Now with PointCTRL I will have to relearn things. This also means I will get to know the ABRIS in much much more detail. THAT is a good thing. Still getting used to it, and tweaking my calibration. I figure it will take a month of use before it is second nature. now … … :joystick: ….:pilotfly:

LOL you may want to return the unit and get a replacement once HP fixes the problem. This does help. Could you post your settings in game, and have you tired it in multiplayer yet? Thanks for the information.

Miles, Thanks once again. o7

My mistake. I meant a GTX 1080 and a reverb.

Just curious if any has this setup, how it runs DCS, and at what settings. Thanks <><><><><><> My mistake with the title. I meant a 1080 and a reverb.

IT's me, It's me that caused the slow down. Sorry about that to those 40+. A VERY VERY big thanks to Miles for helping figure out what the conflict was. No (for me) to try and figure out what caused it. I will also say that these delays will help everyone down stream with avoiding problems, headaches AND make the product better. I went through one myself and FULLY understand. Miles - Keep up the great work. PS - I will post more about my problem and my setup to see if anyone can help see what the conflict may be.

They were in on it also. :)

Oops started with wrong quote.

Miles,' Trying to upload a short viedo of cursor calibration, step 1 (or 2) 20190721_200556.rar

Hi Miles and all, This is the problem that I posted about yesterday. Sorry for the wall of text. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I am having problems with PointCTRL. I have the latest firmware version installed and have been through the calibration process three different times, including the Edge calibration process. It isn’t a problem with the calibration process or getting the FCUs to work in game. I think it has to do with the PointCTRL going outside the window and “loosing focus”. Here is what I am seeing. I go into a DCS FA-18 mission get it up and running and use the FCUs to flick some switches. After a bit, I notice the “ESC” key doesn’t work, some of my HOTAS keyboard command aren’t working as (e.g., nosewheel steering). At first ALT-TAB will cycle thro8ugh the open windows. Once I select the open DCS window, all works fine, for a while. When the key board isn’t working, the FCUs still work to flip switches and such. After a while, the keyboard stops working altogether even after I exit DCS. I have had to reboot to get keyboard input back. =-=-=-=-=-=-= Here are the test I have done so far. =-=-=-=-=-=-=-=- PointCTRL Test July 21, 2019 Test 1, 2, 5, and 6 were done without recalibrating from 7//20/2019. Test 1 Moved Task bar from bottom to right side. Apps running – TM TARGET for Warthog HOTAS running FA-18 script, Oculus Tray Tool, SkatZilla’s DCS Updater Utility , and Oculus home itself. With the exception of Oculus Home, all other apps were minimized. All desk top icons are hidden. Mission: Instant Action, FA-18 Free flight, Caucus Map Test – Launched mission with FCUs off. Flew around tested keyboard keys, ESC key, and programmed stick that issues keyboard commands. All worked fine. Used mouse on ARM key and UFC. No issues. Looked out left side and clicked in mid space. Test keyboard again and worked as it should. Looked out right side and cursor was not steady but bounced around. (See test #2 for additional information. Turned on FUCs and clicked ARM switch. Tested keyboard ESC key and it did not work. ALT tabbed to reset focus. ESC did work AFTER I clicked back in the cockpit. TM stick commands worked, could click on buttons with FCU. ESC command was sporadic. Exited out of DCS and then went back in to see if it was just turning on the FCUs. Once back in with the FCUs OFF, the ESC button did not work. Exited back out and tried Word. Keyboard did not work, it was as if a Function key, or ALT key was stuck 0on. Test 2 Rebooted PC. FCUs off Apps running – TM TARGET for Warthog HOTAS running FA-18 script, Oculus Tray Tool, SkatZilla’s DCS Updater Utility , and Oculus home itself. All apps including Oculus Home were minimized. All desk top icons are hidden Mission: Instant Action, Free flight, Caucus Map Test – Launched mission with FCUs off. Flew around tested keyboard keys, ESC key, and programmed stick that issues keyboard commands. All worked fine. Used mouse on ARM key and UFC. No issues. Looked out left side and clicked in mid space. Test keyboard again and worked as it should In my computer room, there is a sliding glass door to the right. In the setup test, this did not trip the HMU sensor until I was about 45 degrees from looking straight ahead. This time, when I looked to the right side, I first covered the HMU sensor with my finger. When looking right with my finger over the sensor, the cursor was steady, just like looking out the left. As soon as I removed my finger, the cursor, started bouncing. When I look back at the monitor, the cursor was stuck to the upper right-hand corner. A mouse press released it from there and the cursor moved freely around the screen. HOWEVER, the ESC key did not work, my other keys were sporadic. Test 3 – outside of DCS with PointCTRL turned OFF Test with FA-18 TARGET Script running. I had a similar issue once used, it seemed like a key (ALT, CTRL) was stuck. Test 4 – outside of DCS with PointCTRL turned OFF Test using US_helo TARGET script running. I did not see any issues using the limited set commands. seemed to work fine. Test 5 Rebooted PC. HCU and FCUs off Apps running – TM TARGET for Warthog HOTAS US-Helo script, Oculus Tray Tool, SkatZilla’s DCS Updater Utility, and Oculus home itself. All apps including Oculus Home were minimized. All desk top icons are hidden Mission: Instant Action, KA-50 Free flight, Caucus Map Test – Launched mission with HCU and FCUs off. Flew around tested keyboard keys, ESC key. I did not use ANY of the joystick buttons that issue keyboard commands.. All worked fine. Used mouse on ARM key and UFC. No issues. Looked out left side and clicked in mid space. Test keyboard again and worked as it should. Turned on the HCU (held left button for ~ 1 second). Tested keyboard and no issues. Tuned on FCUs. I noticed problems as soon as I turned on the FCUs and before I clicked on any buttons. ESC key did not work, other keyboard commands didn’t work, could click in cockpit. Once I atl-tabedd out and back in the first mouse click brought up the ESC menu. Clicking made it go away, but wouldn’t work again until you click in the cockpit again. Went back out and tested in Word. Again, it was like an alt key was stuck on. Test 6 Rebooted PC. HCU and FCUs off Apps running –, Oculus Tray Tool, SkatZilla’s DCS Updater Utility, and Oculus home itself. All apps including Oculus Home were minimized. All desk top icons are hidden. TM TARGET for was not running for this test. Mission: Instant Action, KA-50 Free flight, Caucus Map Test – Launched mission with HCU and FCUs off. Flew around tested keyboard keys, ESC key. All worked fine. Used mouse on ARM key and UFC. No issues. Looked out left side and clicked in mid space. Test keyboard again and worked as it should. Turned on the HCU (held left button for ~ 1 second). Tested keyboard and no issues. Tuned on FCUs. I noticed problems as soon as I turned on the FCUs and before I clicked on any buttons. ESC key did not work, other keyboard commands didn’t work, could click in cockpit. Once I atl-tabedd out and back in the first mouse click brought up the ESC menu. Clicking made it go away, but wouldn’t work again until you click in the cockpit again. Once you did this the other keyboard commands worked fine. The normal way ESC works, is that you press it once and it brings up the menu, press it again, and it goes away. Once I start having issues, this does not happen. Went back out and tested in Word. This time Word had no issues. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I plan on starting from scratch later today, reinstall the latest firmware, recalibrate and rerun the test above (at least 2, 5, and 6).

I think you were reading my mind. As a previous post stated, I am having issues. I started to post the results of 5 test I ran this morning, but it is rather long. I can setup a Discord channel for Point CTRL, make you the admin (along with me). Once you are comfortable using Discord, I can give you full owner ship. Let me know how it is best to send the test results I have to date (I still have a problem) and if you would like me to establish a Discord channel.

Miles, Yes the headset is active when I calibrate. I put a little piece of paper over the sensor in the Rift CV1 and then set it next to me. I am not sure you can do the first two steps without it being active. I am out doing errands for the next three hours, but will try again later today. Thanks for the response.

Hi, I am having problems with PointCTRL. I have the latest firmware version installed and have been through the calibration process three different times, including the Edge calibration process. It isn’t a problem with the calibration process or getting the FCUs to work in game. I think it has to do with the PointCTRL going outside the window and “loosing focus”. Here is what I am seeing. I go into a DCS FA-18 mission get it up and running and use the FCUs to flick some switches. After a bit, I notice the “ESC” key doesn’t work, some of my HOTAS keyboard command aren’t working as (e.g., nosewheel steering). At first ALT-TAB will cycle thro8ugh the open windows. Once I select the open DCS window, all works fine, for a while. When the key board isn’t working, the FCUs still work to flip switches and such. After a while, the keyboard stops working altogether even after I exit DCS. I have had to reboot to get keyboard input back. I did do a test where I point out of the cockpit at my 9 o'clock and clicked on the runway. When I did that, the ESC key didn't work. I thought this might be because I hadn’t calibrated the windowed constraints correctly. I have done that twice since. I have noticed that in this step of the calibration procedure, I see three flashing cursors on each side of the screen. These don’t seem to appear that I bring the cursors closer together. Another item of note is that I do run with the task bar at the bottom of my screen with several icons in the task bar. Any and all help will be greatly appreciated.

Hi Foxdelta, I didn't seem to have that issue and could do thinks like program the countermeasures program in the FA-18. I did do the edge calibration this morning and it does help to stabilize things. Mine still moves some, so I will probably have to redo. In reading through the pdf my impression was that it was VERY involved and would take a lot of time. AS it turns out it isn't all that complicated and took about 5 minutes. I also suspect my time will improve as I run through the calibration again. So I guess my new bottom line is, do it which ever way you think will work for you the best. the Edge calibration is not all that involved and doesn't add that much time to the initial calibration. BUT bottom line is get it set up and start playing with it.

Thanks for the hints, mariner3302. I am not one of the "instant "Can't fly without them" crowd" but they have certainly peaked my interest. I tend to be more in the "wait and see" camp. The first two weeks I had Track IR3, I hated it. After that I couldn't live without it. Similar thing with my Rift CV1. first couple of weeks , it seemed like a neat novelty but wasn't sure I wanted to fly with it all the time. Haven't flown flat screen in over a year. So far I have used them about two hours in DCS. From that I can tell it will take some time for me to get used to it. I found a few times I wanted to go to the mouse because it was more efficient as I know how to use it. I stuck with it and it got a little easier. Also I haven'[t gone through the Edge Calibration yet, and I know that will help. It will take time to know what button to press when without thinking about it. And to develop a pattern on how to re-engage the FCU. If you are like me, then give then take the time to learn to use them. I also agree with what mariner3302 said in an earlier post. when you get them, go through the first calibration part and then start using them, just to get the feel of them, determine which button you want for the left and right, and get the feel of the mouse wheel emulation. It will be well worth your time. Any way, if they don't make you feel instantly like "I can't fly without them", then make sure to take the time to learn how to use them. my 2 cents worth.

THANK YOU for being so responsive!!! :thumbup: That keeps us :joystick: :pilotfly:

Although I agree it could have been communicate better, and certainly when it was ordinally released, but the facts are 1) it has been released to OB (if not stable at this point), 2) it did not have the impact they were hoping for, and the impact was sporadic, and 3) they aske d us top test to try and figure out why it didn't work like they thought it would. Only thing I am doing now is waiting, watch, and hoping. o7

I play both, as they both have different aspect that I enjoy.

Yeah, the cable is a little weighty, maybe doubling the mass of my CV1. Also not the most convenient for room-scale games that I play as well.. However, with that said, it is pretty neat. Also there is no version 2 without a Version 1. :-) I couldn't agree with this more. I have played around with it for about 30 minutes. I am waiting for the next firmware version for the windowed mode, so why the heck not. It will take some getting used to and "muscle memory". Right now I have to stop and think which button to press for "left mouser", "Right mouse" not to mention using the mouse wheel function. Also it is a little bit "where the hell is the cursor now". Also have to remember to turn them back on after the time out. You can go through all of this and determine what YOU want as mariner said.

Bump. Still hoping to get some information.

Hi, OK so I got my PointCTRL devices Friday, and finally got them calibrated this morning (was busy doing work around the house. It does help if you read and understand the instructions. Sequential means just that. One at a time and in order! Took me three times three #$%^ tires before I realized what I was doing wrong. I was expecting to see five numbered cursors on the screen. :doh: Went back read the instructions a fourth time and there it was. One cursor at a time starting in the center. Reading the instructions multiple times and Farmer Tom's post does help a lot. I haven't done the Edge Calibration yet (waiting for the next firmware and windowed mode) but can already tell it will make a large difference. I also have not tried the ZOM function. Can someone tell me what this does and how it works. I currently have the VR Zoom function mapped to a button on my HOTAS. Is there an advantage to the PoointCTRL Zoom function. Also, from what little testing I have done it appears that the VR re-center function has no impact on PointCTRL. Is that correct. Now to go test more. :pilotfly:

Go to the first post on the first page. The spare parts list is with the ordering suggestion.

Hi, I just got my PointCTRL today and am have read through the Instruction Manual ion Calibration. Let's Just say I'm Thick as A Brick. My question is do you go through the calibration procedure twice, once for each FCU or just once? ANohter question. IT is recommend to run in full screen. Is it necessary to do this each time you start DCS or is there a settingin DCS for this (besides the key stroke) Another item of note. It is probably obvious to most, but I have learned it is best to point out the obvious. I would suggest adding in somewhere that the LEDs towards you and not the screen. Also curious if mounting the HCU in front of the HMD was considered, similar to Track IR setup. I am sure there are pros and cons. Looking forward to getting it up and running.!!

All, I am starting to look at upgrading my GPU. Most likely will settle for the RTX 2080 Super. My only real question is how much VRAM is needed. I have a 1440 P flat panel so I think the 8 GB would be fine for that. I also do VR. Currently I have the Rift CV1 but most likely will up grade to one of the more recent headsets, HOP Reverb or VALVE Index. With VR improving, and the resolution increasing, how much VRAM is needed? Will 8 GB be sufficient. I know more is better, but the cost of the Tis Is $400+ more. From what I have read, if you exceed the VRAM then you will either get stutters or a massive hit in frame rate. Also understand such things as AA, PD can really increase the memory need. Is there any good information on how much VRAM DCS takes for 1) 1440, and 2 (most important) VR? Thanks!

I was in the 18 both before and after.