Jump to content

MilesD

Members
  • Posts

    968
  • Joined

  • Last visited

Everything posted by MilesD

  1. @Skunk160, So glad to hear that. I am moving towards a factory calibration for each manufactures headset to make things easier initially. @Chic, Your long awaited SMS Mount. Its printing as I write this. It should go out tomorrow with your kit. Let me know the next time you are in Wallingford. Miles
  2. Bug Report: AKA Clutter reported that during calibration with the CV1 the cursor targets would disappear before he was able to click on them. I believe this was because the lower resolution display was not registering the code generated micro cursor movements to keep it active. I have increased the pixels the cursors move in the update that will be up in a few hours. Thanks, Miles
  3. Hey FlyinFriend and Chic, I am making a fixed adjustable mount for you to test, The best mounting position is above your headrest facing the monitor. It only needs to be high enough to get a clear view of the lowest position your finger will be pointing. Calibration Procedure is the same. I just dont have the time for track IR compatabilty right now, but I hope to intergrate so the cursor will stay on the control when your head is moved the way it does in VR. Here is a pic Miles
  4. Firmware Update: Two versions of the firmware update are now available, with and without FCU zoom support. Some systems may have a conflict with multiple keyboard emulators, so now you have the ability use PointCTRL as a mouse only emulator to avoid conflicts. Preliminary data shows that may have been AKA Clutters bug. Also fixed the annoying inconsistent left cursor during cursor target setup in calibration mode. The left cursor would slightly jump left on button release. I think I spent 30 hours on that thing. It wasn't even my code that was bugged, it was a compiler corruption. Damn
  5. This does not change anything. And you can calibrate either way you want. One way you are moving your finger to the cursor, the other way your just moving the cursor to your finger. Works the same way with any cockpit and the stettings are universal from one aircraft to another. The alternate method just does better math because its getting the XY and Z calibration data from where your hand will actually be during normal operation. That being said, I would expect if you calibrated for a helo and used a rotary dial on the overhead console, you would have a reduced error at the edges of the FOV. Reference your question about siting back after recenter. As long as you calibrate after the recenter and are seated back there should be know issues. Thinking about it, It may not matter at all, same as if you were skewed in the cockpit when you calibrated, it should not mater, but I will test. Miles Thanks, I will do some more videos with other aircraft, same procedure. Miles
  6. Your always helping, I would be so far off task without your constant "stay on target" "stay on target" from the cockpit of your x-wing. I hope you know I was joking only the way friends and "Brothers in arms" can. My wife actually pointed out it could be taken the wrong way. I said, "Not Dan, I'm sure he got a good belly laugh out of it. Just in case anybody else didn't get it, It was an inside joke to a friend. Miles
  7. Hey FarmerTom, Your suggestion about using the cockpit for reference, and later feedback about arm position got me thinking about different procedures. In the early morning hours last night, I tried an alternate method of calibration using cockpit objects for reference as you suggested, rather than just pointing and clicking on the cursors. The results were outstanding, and when done properly can eliminate the need for edge calibration. By using your idea of actually pointing at objects, coupled with positioning your hand at the distance where it feels like you are actually touching the switch many of the variable tolerances are reduced. The best part was no coding changes, just a alternate procedure to try out. Thanks, and I think this was that synergy you were talking about. I was worn out in this video, but I wanted to get a demo up showing the alternate procedure. Miles
  8. Okay, After reading through you process, all of the issues seem to be related to IR interference and the cursor box window wich is causing a loss of DCS window focus. The escape key doesn't work, because the escape key dosent work when you loose focus on the DCS window. I.R. interference is just like TrackIR. I have been fooled a few times by the sun shifting and bouncing off a shiny object. Did you move the cursor window box far enough inside the DCS window so you could see all 4 cursors clearly? I think I suggested in a PM that you try moving them inward until you can just see them in your headset, and then move them out just out of view. Losing focus when looking to the right makes complete sense, because the IR source from the window was being picked up as the cursor, and when you clicked,it it was to the extreme right outside the field of view. A quick pic or short phone video of your cursor box set-up would be really helpful. But I concur with what you said about losing focus. Narrowing up the cursor should completely eliminate your issues. Good luck and feel free to give me a call on my home phone, I will PM again if you don't have it. Miles
  9. Out to dinner with the family now but I will read and digest when I get back
  10. Hey Clutter, Share it here, it may help someone else. My experience has been the task-bar will pop up even when its hidden and cause a loss of window focus. I always have mine on the lefts side, I feels more intuitive to me because you are always looking and working in the vertical. But that would not cause your issue with pointing out the extreme right side to lose window focus.
  11. So here a few ideas for customer support, 1) A short phone video showing the screen and possibly FCU with audio narration of what buttons are being pressed would significantly shorten my troubleshooting time. Alternately a desktop video capture with audio narration of what buttons are being pressed might be easier, I believe we all have that capability with windows 10 game-bar. It would probably take the user less time than all of the back and fourth descriptions of what is going on. 2) It would be nice to have a central posting area specifically for these videos so everyone could provide assistance. It will probably entail uploading to your own you tube account and linking in a support page on pointctrl.com 3) I will make some more videos to include showing fails and what causes them, as well as the fix. 4) I was thinking of some form of office hours live stream for support. it would be a lot easier for me to sit here and do my work and if anyone has a question I can turn on the camera and answer questions, if no one comes to the live stream, even better. 5) Discord? I don't know how it works, but I don't want to wear out my welcome with ED in this forum. I have sent Wags a PointCTRL a few months back for testing, but I believe he is very busy and has not had an opportunity to test it and we are not in contact anymore. I believe they may be going in a different direction with Capto-Glove. Which to be honest, is a much more professional and long term solution than PointCTRL. They have a team of experienced true professionals in this field, compared to some random retired Green Beret on the internet who probably has no business making this stuff, but just wanted to point at stuff in his cockpit make it work when playing a video game. Although, I was contacted by U.S. Air Force contracting for an order. Funny story, A few months ago, Sen-Huang Huang, the Founder, Chairman, President, and CEO of PixArt, the company that makes the PointCTRL sensor (and pretty much every mouse sensor in the world) flew all way from Taiwan to spend the day with me in my living room to talk about PointCTRL, and how one random guy who was not an engineer, was able to make PointCTRL work. He is truly a gracious and inspiring Man. Sorry off topic. I welcome any other suggestions to make PointCTRL a better experience, and as always, thanks for your patience and input. Miles
  12. Hi Kaltokri, Thanks for the question, and the accurate observations about the slowed pace of shipping. As users with more diverse experience and systems use PointCTRL new issues present themselves, such as ease of calibration, headset reporting, multiple monitors ect. I need to work on a self help section of the manual describing problems and fixes. I would encourage everyone to watch the videos on the website before receiving PointCTRL so you are familiar with it. If I just focus on production I can ship between 5 and 10 units a day. However that would compound the customer support issues. I am trying to get ahead of the curve so users can have a better experience with PointCTRL. I am going to do a post with ideas for customer support for some feedback. Thanks, I am sure you asked what many others were thinking. Miles
  13. Hey Clutter, When you are defining the left and right cursor box limits, ensure the VR headset is active, I usually just put mine face down and throw a mouse pad inside to activate the proximity switch. When the cursors are close to the DCS window they offset significantly and apear to jump around, continue to bring them inboard (closer together) until you can just see them in the VR headset, then just move them out a bit. It sounds like they are to close to the DCS window edge. Keep me posted, Miles
  14. He's an angry Elf "insert Miles Finch clip"
  15. Hey FarmerTom, I don't know if this pic makes any sense, but it gives a general idea why we have to calibrate to ensure the cursor moves to where we are pointing. We should not have any feedback, if we did, it would just show a cursor that was not aligned with our finger. I have used a few different methods but this seems to give the best results. When completed the position of your arm should align with the cursor in any cockpit since we are mapping the the global FOV of the V/R environment to global FOV of HMS. I hope that helps. I do have one that works completely different that I will probably add in the future as an alternate method that you can select when the GUI is done. Just make sure you calibrate with your hand at a distance from the HMS where you will usually use it in the cockpit and you should be good.
  16. That's a good question FarmerTom. I've been wanted to include a picture in the manual for a while illustrating the simple geometric relationships, and why we calibrate. While I like your thinking about scaling the panel it does not correlate well to what we are specifically trying to achieve. As far as your arms being outstretched, do what ever is comfortable for you, I don't extend my arms all the way, I calibrate where my hands feel like they would be touching the panel and controllers in front of me. In my case that's slightly bent. It really does help me with muscle memory and immersion when I use my hands at the distance where I perceive the the panel or switch I am interacting with to be. It's what I have worked so hard to make PointCTRL feel like with a 2d mouse. I do cheat on some of the switches low on the center panels of aircraft that are hard to reach. I will do a quick sketch that may may things more clear, Thanks and don't take offense at Mariner, I know him well, and he has been a huge help to me, that's just his default conversational Marine Speak.
  17. All great points, and I am happy to see everyone sharing. Just a note, edge calibration enables fine tuning if you were not pointing directly at the cursors during normal calibration. It is not a separate algorithm and only allows adjustment to where your finger was pointing during the calibration procedure after the fact. A good initial calibration may not require any edge calibration. Please don't forget the practice video and procedure that corresponds to the picture at the end of the manual.
  18. Critical Update Critical Update Mariner3302 found a mistake in the calibration function, There was an issue with adjusting the cursor targets. You were unable to move the cursor targets left with the FCU during calibration. Please update with Version 071919 Thanks and apologizes, Miles
  19. Your good Virus, I stopped shipping until I had the DCS center windowed view working and documented. Calibration was proving to be a bit of a challenge. I think its much better now. I just started sending invoices again, yours should be coming soon, Thanks for your patience, Miles
  20. A video on FCU strap adjustment and charging I will start shipping again Wednesday. Thanks, Miles
  21. Hey Panther, I missed your stacked monitors post. I wrote the code but didn't get a chance to test it with multiple monitors. did it work out as expected? Miles
  22. that's actually a good point to bring up. you can reset pointctrl by pressing the white button on the HMS at any time . if you lose your place during a procedure it's always good just to hit reset. EDIT just to clarify, pressing the white button once just reboots pointctrl , compared to holding the black buttons and pressing the white button which resets all of your settings to the factory default Rift S QUOTE==Panther=;3980910]Good old pc reboot solved the issue. I thought I rebooted after firmware update, but maybe I didn't. Either way it is resolved, sorry for the false alarm.
  23. Trying to do this on my phone, are you in the v171619 in center window? Were you able to reduce the width of the cursor targets to fit the CV1. I assume you downloaded the new PDF manual v071619
  24. Password inbound, Sorry about that, it was supposed to be the packing slip and email. I will fix that. I have a know bug that I spent the day trying to fix with the new firmware. I am just going to post it, as is. The bug is minor ans only appears when setting the cursor targets. The left cursor does not move as much as the right cursor when making small adjustments. It may not even be noticeable to most people, and has no effect on final calibration. Miles
×
×
  • Create New...