Hempstead

I suggest you go search in Digikey, like https://www.digikey.com/en/products/filter/angle-linear-position-measuring/549?s=N4IgjCBcoKwCwyqAxlAZgQwDYGcCmANCAPZQDaIcADGABy1whEDMcA7AJxwdMjMwA2KswgsOzKm0ZjaVAEzNe1Zm34gAukQAOAFyggAyjoBOASwB2AcxABfG0TnkQACWxYABHjRo8yHe-xzHGJjDSJEaBAtKDBtaMg5GHsQASQQUwATfQBaMBpeXX1eHQBPLTx9DBxUOyA

Fixed for my Quest Pro. Thanks!

Shapeways declared chapter 7 bankruptcy... in case you don't know yet, https://3dprinting.com/news/shapeways-files-for-bankruptcy/. I will say... buy your own 3D printers. There are just so many things you can print for your flight sim hobby, and other household items. The expensive shipping costs just kills these small item private sales.

One word, latency. Another word, debounce. Yet two more words, guaranteed sub-millisecond. Plus, the real reason is that an RPi Pico has only 4 12-bit ADC channels. One of them is used by the CPU temperature, leaving 3 available. Unfortunately, there are 4 analog wheels on an F-16 ICP. So... facing with having to design a multiplex ADC circuit in the back of the PCB, why not just slap another $4 Pico on it? Makes things so much simpler, and cheaper!

Doesn't work for me. I had Developer mode turned off on my Quest Pro, didn't work. I turned it on, and tried. No dice. Turned off again and tried, no dice either.

Same here, Quest Pro. Makes the game completely unplayable. 100% epic fail. The Oculus controller does not even show up on the Control Setting page as a column. Just completely non-existent.

The 2nd stage mechanism of the trigger now finally works after weeks of struggling. Had to use my mini-lathe to make two key parts in brass! Too bad, couldn't make 3D printed ones work for these two. That makes the bar for you to make it at home much higher. https://blog.hempstick.org/2024/07/f-16-and-other-modern-jets-two-stage.html

F-16 ICP analog wheels prototype completed. https://blog.hempstick.org/2024/07/f-16-icp-analog-wheels.html

Just received the ICP PCBs. It fits perfectly! I am still waiting for the newer version of Hall sensor PCBs ordered from OshPark (and the main ICP PCBs too, which I forgot to "unmask" the main contact rings of the dome switches; so I will have to grind them off). The ICP main PCB is designed with KiCAD (I have ditched EagleCAD since AutoDesk acquired them.). The Hall sensor PCBs, however, are years old so it's still in EagleCAD format. https://blog.hempstick.org/2024/06/f-16-icp-pcb-made.html

via Steam only....

Optical Trigger prototype. https://blog.hempstick.org/2024/06/optical-trigger-module-prototype.html

F-16 ICP mechanical design fully prototyped. Made with just a 3D printer, and a laser engraver, plus some common hand tools, like screw drivers, needle files, tweezers, paint brushes, cotton patches, etc. Next up... PCB design finally! Without fixing the mechanical design, I couldn't start designing the main PCB, because I wouldn't know where the screws would be and to avoid for routing traces. https://blog.hempstick.org/2024/05/f-16-icp-mechanical-design-fully.html

I am not 100% sure... but what I have been seeing this past week is that the Kola map triggers it particularly often. But it seems to be cause by Oculus runtime. I don't turn off my computers... so since the latest release of Oculus runtime update... If I leave Oculus desktop runtime running (I usually do) for a long time, then the kola map triggers it almost every time. But, this also happens to even the NTTR map now, which never happened before. Now, if if happens, not matter what I do it will have very low FPS, even if I quit the game and go back to the welcome screen of DCS, I get 15 fps (with a 100% GPU usage). Eh? There shouldn't be much 3D rendering going on when I am in the welcome screen! And it will persist until I quite to desktop and come back. However, if I don't restart Oculus runtime, and launch DCS again, I will get 45fps (I set the limit to 45fps) in the welcome screen. But as soon as I get to Kola map again, it will trigger immediately. But, if I restart Oculus... or reboot, other maps will be fine... but Kola will trigger it if I head toward the sea of Kemi. So, this all seems like some VRAM leak problem. But I have not really isolated the problem yet... It's just that Kola seems to be the sure way to trigger it.

I have a bucket seat... I kind of regret that... I am doing F-16 VR, and it kind of interferes with the arm movement when trying to access the rear side panels on both sides. Yet it doesn't interfere with pedals. However, the side support does have an advantage... when you use non-force-sensing sticks like the Warthog to take advantage of proprioceptive sensory in your arms, it serves as a support for your arm such that when you pull turns. It steadies your arm, instead of building an arm support of the F-16. It does interfere with my throttle movement in the rear section a bit, not much. And it's not like you use that section very often anyway other than in cold start, or parking. So, I guess it's ok to use a bucket seat. Just keep in mind that it does interfere a bit. Also, keep in mind that... if you are trying to build a VR pit that has all the switches in the right place as in VR, you have to watch out for the width of the seat. Most of the car racing seats I can find online are too wide. They eat into your F-16 panel space. The only one I can find that is narrow enough happened to be a bucket seat, so.... And no thanks to suggestions of building a 1:1 very uncomfortable ejection seat. brrrr... no. Putting up with uncomfortable equipments is for young bucks... not for old farts.

In an F-16, Intel Core i9 7900X (10 physical cores, 4.2GHz), 64GB RAM, RTX-3080, and a Quest Pro, Win10, all SSD-M2. I rate limit it to 45fps in DCS VR... and am able to get 45fps in NTTR map.

Starting hot on runway of Kemi Tornio... 7 fps... Starting at 6,000 agl over Kemi Tornio heading north, 33 fps... turn around heading toward Kemi Tornio... as soon as I get close to the town, 22 fps, and terrible, unplayable flickering.

I got 7 FPS in VR, far worse than Mariana.

ICP letter painting... Dobber, and analog wheels. https://blog.hempstick.org/2024/05/icp-letter-painting-dobber-analog-wheel.html

ICP mode buttons 2-tone 3D printing. https://blog.hempstick.org/2024/04/f-16-icp-panel-2-tone-print.html

An F-16 ICP Design Test Assembly video Note that the thinner yellow plate is a PCB stand in. The PCB can only be designed after all the mechanical design is done and tested for assembly and some durability. I mean, I have route the traces around the screw holes... I have already moved the screws a few times already for assembly problem. Moreover, I have not decided on what I am going to use for the sensor of the 4 analog wheels yet.

F-16 ICP "design" render, WIP. https://blog.hempstick.org/2024/04/f-16-wip-icp-render.html

F-16 ICP Button Test https://blog.hempstick.org/2024/04/f-16-icp-button-test.html

Successful tests of the F16 TQS friction generator. https://blog.hempstick.org/2024/04/f16-tqs-electronic-friction-generator.html

Here this guy says it can be done... his files are from SW 2021. So, assuming he's correct, then perhaps your files are too old? I have a full license of SW2023 Premium. I can convert your older files to 2023 format and see if that helps in importing into SW for Makers. Ping me by DCS forum messaging system.

I have the same problem with OnShape. I used to recommend people using OnShape to import my models to see the dimensions and to export them to other formats... not anymore after they whacked the free accounts' 2-free-private-projects. I have a problem with that! I mean, you import my CC International Non-Commercial model, and it automatically gets "published" as public... what about the license? Are you stripping the CC non-commercial license? That's basically violating the license agreement. How do you respect the original license agreement and do attribution required by the CC license? I have no idea! The worst for the new OnShape free account is that now no matter whether you are ready to publish... an work-in-progress project is also shared publicly... I would say, try Solidworks for Makers https://www.solidworks.com/solution/3dexperience-solidworks-makers at USD $45/year. There are limitations... like you may not use it for profit, and the files created will not share with full Solidworks and vice versa. I know, it's not free... but $45/year is rather reasonable. I mean, think of it as paying for the infrastructures required for your account. Then, you use Fusion 360 free for importing and exporting..... Note that, I do not use Solidworks for Makers myself... so my recommendation for Solidworks for Makers is "on-paper". I paid for a perpetual premium license.