Jump to content

MilesD

Members
  • Posts

    968
  • Joined

  • Last visited

Everything posted by MilesD

  1. Repost from discord Hey guys, Apologies for the not being on here. I recently have been dealing with a medical issue, and PointCTRL may be going away. I will do my best to take care of any current issues, but right now I'm not sure what what the future holds for it, and I don't know when I will be back on here to respond. Thanks, Miles
  2. Hey Sirrah, Repost from the PointCTRL Discord... You will be fine with the offset. The HMS sensor has a wider FOV than the Reverb. You may want to angle its slightly inward so its looking directly at your finger when it is extended. A recalibration may be necessary. Let us know how you make out.
  3. Hey GoonEb1rd, Sorry to hear your PointCTRL is giving you a problem. It sounds like IR interference from sunlight or lamps. PointCTRL is sensitive to IR interference just like TrackIR, even more so, because we look all around when using VR. The cursor movement being reversed is usually caused by a bad calibration and should go away with a default reset. When doing a default reset be sure to wait until the cursor jumps to the middle of the screen, and then begins moving from left to right before you release the "Set-Up" button after tapping the "Reset" button. An easy way to check for IR interference after a proper default reset, is to go yo your desktop (not in DCS), activate a FCU, and immediately put the FCU out of sight of the HMS (Head Mounted Sensor). Then move the headset around looking for for cursor movement on your desktop. If you move your headset headset around until the cursor is in the middle of your monitor, it should be facing the source of IR interference. Don't forget the HMS will only remain active for 15 seconds after the last button press. There are a few thousand of us on the PointCTRL Discord and it's a great place to get assistance. The guys are always picking up my slack and answering questions before I get to them. I also like to solve things quickly on Discord voice. https://discord.gg/MTvsNq2yHw Here is a good way to test PointCTRL on your desktop. Let us know how it goes. Miles
  4. Here is what the Crystal mount looks like. There is lot of info on our discord also. https://discord.gg/Qu87sb7b
  5. Hey Snacko, Just slow steady pressure seems to work best. If your getting a new mount, you don't really have to worry about removing the old one. The HMS PCB just pops right out so you can put it in a new mount. The Pimax Crystal mounts are available on the site for $8.00 USD, or I can just send you the STL files if you have access to a 3d printer. https://pointctrl.com/product/hms-case/ Just let me know, Miles
  6. Yes on the first line. HTCC has a different look and feel, but it's usually only used as an alternative if you don't have PointCTRL or want to use it in MSFS. The PointCTRL wireless HMS is for for headsets that don't support hand tracking natively, or for people who want a plug and play solution. The APBs are attached to the HMS, so they wont be on the headset if you use it as a button press receiver. Hope that helps.
  7. The advantage to using Freds HTCC is to make it wireless and compatible with MSFS. You can use the Freds HTCC software and the special PointCTRL firmware he has on his site. It will use the Q3s hand tracking and use the PointCTRL FCUs to send the button presses. The HMS just has to be plugged in to a USB port on the PC. It only uses it as a dongle for the button presses, not the tracking. I was just talking with Fred and meant to ask him if that's what we did, but forgot. I am pretty sure that's how it works, but I will double check when I get home. Miles
  8. Hey Nessuno0505 Slughead did a nice job on his unit, and it's available now. I have been in slow mode for a while with some physical challenges. I just put the order in for the newly designed PCBs for the FBU's (Finger Button Units). These are long overdue, as Fred and I talked about them when we were moding the PointCTRL firmware for use with his awesome HTCC software. The new FBUs are Bluetooth direct to the PC, and look and operate similar to the current PointCTRL FCUs, Just a bit lower profile. I expect to price for them to be around $50.00 USD each. They are still probably about 30 days away. There won't be a waiting list for these units as I don't expect much demand for them, and they will be ordered directly on the PointCTRL website. I am using the same tech on a PointCTRL version 3 which will make it much easier to manufacture. I have been meaning to do this for a while but just did not get around to it. I hope this will increase the production speed 5 to 10 fold. There will be no functional difference between the current PointCTRL 2.5 and PointCTRL 3, however the new version will allow me to add a wireless HMS shortly after the release of PointCTRL 3. So for now, Slugheads "SlugMouse" is the best option for using Freds HTCC software if you don't have already have PointCTRL. I think Fred and I made the PointCTRL HTCC firmware so you don't have to have your HMS mounted, it just works as a dongle. Sorry this was a bit rambling, but wanted to share where we are with PointCTRL. Miles
  9. Don't forget the FOV Tangent Multiplier. I run mine at 0.8;0.8. It reduces the number of pixels being processed by 36% without compromising anything. I wear glasses and 0.8;0.8 is my max before I start seeing a flat edge at the top or right side of FOV. This allows max render resolution in the oculus app. I don't add any upscaling in DCS. Edit: missed it was already mentioned.
  10. Hey Guys, Here is the latest iteration of the FCUs that are now shipping. Improvements: 1) Reduced size. 2) Added support for the IR LED . It no longer can be pushed into the FCU case my mistake. 3) New magnetic charger with rotating and pivoting head, and a power indicator built into the cable. If you ever need to, you can charge these while flying. As always, thanks everyone for your continued support and patience. Miles
  11. Awesome post! This is very helpful, as I was struggling a bit with this exact switcholigy on my first rocket run. Many thanks for your time spent to make this so clear. Miles
  12. Just a quick shout out to say Eagle Dynamics customer service is awesome. F4E day came and I did not see the module in my system. Turns out, I had mistakenly made a new account and put my last three pre-orders in it. ED quickly sorted it, moving everything to the proper account for me. Thanks again for the quick reaction time and simple interaction to solve my mistake. Miles D
  13. You can track the currently shipping Pre-Orders in the Discord server. I had a stop in production for a bit with a move, but we have recently been shipping about 10 days of Pre-Orders every 5 days. I plan on increasing production again very soon, but at the current rate, the wait would be about be about 10 months. No payments are accepted until orders are ready to ship. Thanks, Miles
  14. Hey DD, Did we get this sorted on Discord?
  15. I have to be sure the Meta app is running on my desktop before I turn on the headset. Whenever I forget, I just get the spinning circle and no connection. (I only use the cable) Miles
  16. Hey Jurinko, It usually varies from 2 days to 2 weeks, sometime things pop up that can delay it more, like a mount request that is has not been made yet. I just had one delayed for about three weeks because we did not have the Pico mount designed, but I contact the guys with those types of situations. You should have received delivery by now, Please DM me your email address or name and I will check it. Thanks, and apologies for the delay, but we will get it sorted. Miles
  17. Unfortunately it's been 4 or more years since we have used those batteries, and I don't have any. The new batteries are custom made and use a smaller connector. Appreciate your efforts and sharing.
  18. That mah may be is to low 150 is better. I think this may be the exact replacement, https://www.aliexpress.us/item/2255800153846161.html?spm=a2g0o.detail.0.0.53e61fed0NCEiO&gps-id=pcDetailTopMoreOtherSeller&scm=1007.40050.354490.0&scm_id=1007.40050.354490.0&scm-url=1007.40050.354490.0&pvid=00d14c31-2d11-4ec9-880d-00b47b65601e&_t=gps-id:pcDetailTopMoreOtherSeller,scm-url:1007.40050.354490.0,pvid:00d14c31-2d11-4ec9-880d-00b47b65601e,tpp_buckets:668%232846%238116%232002&pdp_npi=4%40dis!USD!9.56!8.13!!!68.13!57.91!%402103246417048195716591412ea020!10000001394383916!rec!US!110216179!&utparam-url=scene%3ApcDetailTopMoreOtherSeller|query_from%3A
  19. Hey Johnny, Sorry for the slow response, if you pop over to the discord it will be easier to get your questions answered. We slowed/stopped production for a bit, but are back up now. V1 and v2 have different batteries, and v2 has been out for about 3 years now. For v1, the connector is a JST-PH 2.0mm 2 pin and are 150mah capacity. The batteries you linked have 100mm extension and would probably have to be shortened. This one from amazon looks pretty close https://www.amazon.com/260mAh-Rechargeable-Battery-Charger-Quadcopter/dp/B08ZJ4QQMW/ref=sr_1_35?crid=228BOIB0MFGTF&keywords=JST-PH+2.0mm+150+mah&qid=1704477965&sprefix=jst-ph+2.0mm+150+mah%2Caps%2C61&sr=8-35 Good luck with the unit, and let me know if need any assistance with set-up. Miles
  20. Thanks guys, Thanks Phantom, I did change it to 4096,I thought that was the max, but I will check again. Thanks Hadeda, When I turn off sliced encoding I tend to get a mottled mess. What is strange is how the lines gets worse over time. Going to F10 sometimes fixes it for a few minutes. The error seems to stay even after the missing data is no longer an issue. Hopefully they will look at this years old issue soon. It used to alos happen with my Q2 on a different system. Thanks again Miles
  21. Thanks Phantom, I did reset everything to default a few times in the ODT, I will try again though.
  22. Hey Guys, I have been frustrated trying to get rid of these translucent white bars that slowly get worse as I fly. If I look skyward, and just look at the blue, they will go away for about 15 seconds and then slowly come back. As I understand it, they are from the sliced encoding missing data. System: AMD 7800X3D and 4090 3.2 USB-C to USB-C, test out to 2.5Gbps on Oculus Set-Up Headset @72mHz with ASW disabled Best results so far with: Encode resolutions Width: 4096, It may be past the max Encoder: H.264 Encode Bitrate: 960 Mbps Sliced encoding: ON, If I turn sliced encoding off, it's a bit of a mess Has anyone else had problems with these white bars? Thanks, Miles
  23. Hey Honey Badger, Unfortunately the APBs require the HMS to function.
  24. Hey Brabs, There is not currently a way to do that. PointCTRL should only over-ride your mouse cursor if an FCU is active(button pressed within 15 seconds), and in the FOV of the HMS sensor. If my FCU's are active and in my FOV and I need to immediately use the mouse for something, I try and look up and away from the FCUs. Other than that (Left had over HMS, Right hand on mouse, until the cursor times out. Miles
  25. Just took a few different aircraft up for a spin. For me, the Quest3 is a huge improvement over the Quest2 in the cockpit. The outside view does not seem as impressive.
×
×
  • Create New...