propeler

It is on kickstarter yet)) I plan to print something like this https://www.printables.com/model/316629-pico-4-increased-fov-facial-interface-gasket

Wifi - install VD stream app on PC - buy and install VD app on Pico - run streaming app on PC, enter your Pico account name in settings. - run streaming app on Pico, set picture quality - run DCS Profit :)

DCS. RTX 3080 + 5800x3d. Virtual Desktop on Ultra settings(not God mod). Works smooth. Picture is crystal. I think all those influencers are just trying us to sell 4090

RT3080. VD + SteamVR. Works good without any hacks.

My Pico arrived. I do not know how image looks like in G1/G2/8kx, but I can compare with Pimax Artisan. It is day and night. DCS + Virtual Desktop + 150MB. On Ultra(even not god mod) text on MFDs in F16 are easily readable. I do not see any compression artifacts. Definitely need to print new facial interface with slim profile. Original facial interface is weird. FOV with original interface is just not on par. But! I've checked how FOV looks like when to remove face mask and put lenses closer to the eyes. WOW! I was impressed. FOV becomes closer to something in between Atisan's small and medium settings. And picture is clear at 90% of all the FOV as for me. I was very impressed. I think with custom facial interface it would be unbeatable option for the money.

Could you make couple of photos how it looks like through the lens. How readable are gauges in different planes

What do you think about quality of picture comparing to something like Pimax Artisan or Pimax 5k? Artisan has lower resolution but does not have compression. PICO has higher resolution but of compressed video. Will it be picture quality improvement coming form Artisan or 5K to Pico?

How do you p;an to test it? Do you have joystick build on ODrive controller?

It goes well. People building devices their own on firmware I develop. Some of them build from my CAD plans, some adapt it to their needs, some build totally differen mechanical scheme an use only electrical part from my original project. There is FFB pedals project as well based on my firmware. Here are some of them: All of them were built with only litle(or even without) informational support from my side. Software part is evolving too. Because native FFB support is not perfect or is missing in different games I developed a solution for genereting rich FFB effects from game telemetry. Now it supports effect generation for MSFS, DCS and Warthunder. il-2 on the go.

It works based on telemetry. It supports rise of force with speed(natural airdynamic), takes into account prop wash for propeller airplains, has simple spring capabilities(with curve adjustment) and advanced springs based on AOA and G. It also have configurable shaking effects depending on AOA, mechanisation retraction, landing and rolling on ground.

One guy from russian speaking branch of il-2 forum created first FFB pedals! Is future of FFB deviceds coming? What do you think>

As for me the best solution for any kind of modern grips - to use "pass through" approach, when you just use longer cable to native controller. Either VKB, VPC or any other kind. It is the most bulletproof solution. Because modern grips commonly use proprietary not open protocol for comunication, trying to emulate their protocol usually not relayable enough and have different limitations.

Write me to PM.

Just PM me an e-mail. I will send you all needed files

It is not a problem to make it one axis, I have FFB wheel project closeli conected https://github.com/o-devices/bldc-ffb-wheel on similar firmware. The only question is HOW it should behave (I'm not an expert in helis) and which telemetry we need to obtain from the game to calculate this behavior.

It depends on country.... and even on city. And possibility to 'arrange' the cost with a workshop which will be cutting/bending metal.

Could you measure backlash on RMD X8 version? And is it normally backdrivable?

YEs, variable resistors. I use whatever found and then tune them.Them are usually multiturn and can be tuned pretty precise. I did not checked exact value but I think something between 2k and 20k will be ok.

I was looking at those motors. Them are pretty expensive:)

Yes. It will be standalone application with output to directinput FFB device in first version. I already implemented MSFS, DCS and Warthunder telemetry. Working on direct input devices stuff. And "my device" is not my any more

Actually, it is possible to implement A LOT with telemetry provides from DCS. Even basic telemetry. In my firmware I implemented bunch of effects and more to come. There are: - Stick load depending on speed. Natural square curve progression. - Stick load depending on prop thrust, so emulates prop washing of control surfaces. - Artifficial spring based on AoA and G force(obviously with curve tuning) - Elevator weight emulation - Air dynamic center shift effects due to flaps, gear, spoilers retraction. - Turbulence effects due to flaps, gear, spoiler retraction. - AoA and G force shaking. All shaking effects with tunable frequencies and power. - Landing effects. And some more are planned. Expect separate application that can feed any FFB joystick with such effects to be released soon

Yes.

Actually it is there https://github.com/o-devices/bldc-ffb-joystick/tree/main/dcs

It is not needed, but I use it. I use combination of speed, aoa , acceleration and thrust to generate effect augmentation. But normal DCS FFB is prety good on it's own. Especially on selected aircrafts.

https://github.com/o-devices/ffb-joystick-howerboard-motor-base all needed files to replicate v1. Feel free in building your own.