It’s the way the HMCS must be projected. It is always in the center of the screen. If you don’t have a head tracker, by using the mouse to pan for example, the view moves, but the HMCS stays put. VR works the same. the scene gets panned when you move, but the hmcs stays in center view and you are always looking at the center of the VR screen.

No matter if its 1 x ? or 1:1 with TIR, you are always forced to move your head ‘AWAY’ from the center of the screen where the HMCS always resides.

To fix this, BMS would need to use a completely different panning system if a tracker is being used and would need its own ‘track’ profile to be configured for all 6dof’s which moved the HMCS position along with the screen pan (at a different rate). I think it might be possible, but very complex and frankly would probably look and feel weird with image distortion close to screen boundaries (especially in wide format), if not totally nauseating, I think there’s lots more useful features to be added to BMS including VR ( 😉 )

Good morning

Bad keystroke assignation, grrrrrr.

Thanks to all

@SemlerPDX Thank you sir, it works. As always, thank you for quick response.

@luke777 That’s awesome!

The ntdll.dll message is not very specific and can lead anywhere since that basically says that the Windows core is being called. So somewhere in the call tree from TrackIR5.exe down to ntdll.dll some newer graphics drivers messed something up.

All,

As always thanks for the help. It’s now working as I followed comments in thread.

Thanks again!

@white_fang
Thanks, dear mate.

And the point is just that one you remarked:
before attempting to do anything in the registry, you must know what is to be seeked for.
Absolutely and mandatory, this.

With best regards.

<blockquote>@jstnj yeah for DCS and MSFS it does work pretty well but for titles like BMS your only option is FacetrackNoIR with the plug-in. It’s unfortunate. So do you use it with BMS at all?<br /><br /></blockquote><p>No. I don’t use it in BMS, but I want to. I will not install FacetrackNoIR though, because I see many stories of it causing extreme headaches and driver issues for every single other native EyeTracker game. It’s frustrating but until I can use at least Tobii GameHub to make a BMS profile I can’t see myself in BMS very much. <br /><br /></p>

<p>Could it work with OpenTrack ? If so, the motions/movements could be translated to axis for looking around seamlessly like with Opentrack and eg. Delanclip. But no camera required, so that would be very neat</p>

<p>You should set a ‘pause’ button for TrackIR inside the TrackIR software. This way, you can stop TrackIR when you want, and use the mouse to pan around the (#3) pan view cockpit mode. When you want to use your head, you can ‘un-pause’ TrackIR:<br /><br /><img class=“ql-image” src=“https://i.imgur.com/QDskYzw.png” /><br /></p>

@Mosquitoe Wonderful news!

Hi, Here’s my BMS.ini profile. I have no real issues, and have been using opentrack for almost a year. Check out my recent videos.

[migrations] last-migration-at=20180428_00~ [tracker-pt] camera-name=PS3 Eye open driver camera-fps=75 active-model-panel=0 clip-tz=40 clip-ty=50 clip-by=75 clip-bz=70 automatic-threshold=true threshold-slider=@Variant(\0\0\0\x7f\0\0\0\x18::options::slider_value\0@V\x80\0\0\0\0\0\0\0\0\0\0\0\0\0@o\xe0\0\0\0\0\0) model-centroid-x=0 model-centroid-y=0 model-centroid-z=0 [opentrack-ui] guid-center= button-center=-1 keycode-center="=" compensate-translation-disable-x-axis=true compensate-translation-disable-y-axis=true compensate-translation-disable-z-axis=true compensate-translation-disable-source-pitch=true compensate-translation-disable-source-roll=true keycode-toggle=- use-system-tray=true start-in-tray=true [opentrack-mappings] yaw-alt-axis-sign=false pitch-alt-axis-sign=true pitch-max-output-value=-180 z-alt-axis-sign=true z-max-value=15 [spline-yaw] points="@Variant(\0\0\0\x7f\0\0\0\xfQList<QPointF>\0\0\0\0\x4@\x18\0\0\0\0\0\0@,\0\0\0\0\0\0@3\0\0\0\0\0\0@U\0\0\0\0\0\0@<\x80\0\0\0\0\0@a`\0\0\0\0\0@C\x80\0\0\0\0\0@c \0\0\0\0\0)" [accela-sliders] rotation-sensitivity=@Variant(\0\0\0\x7f\0\0\0\x18::options::slider_value\0?\xe0\0\0\0\0\0\0?\xa9\x99\x99\x99\x99\x99\x9a@\x4\0\0\0\0\0\0) rotation-deadzone=@Variant(\0\0\0\x7f\0\0\0\x18::options::slider_value\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0?\xc9\x99\x99\x99\x99\x99\x9a) translation-sensitivity=@Variant(\0\0\0\x7f\0\0\0\x18::options::slider_value\0?\xd9\x99\x99\x99\x99\x99\x9a?\xa9\x99\x99\x99\x99\x99\x9a?\xf8\0\0\0\0\0\0) translation-deadzone=@Variant(\0\0\0\x7f\0\0\0\x18::options::slider_value\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0?\xf0\0\0\0\0\0\0) [spline-Z] points="@Variant(\0\0\0\x7f\0\0\0\xfQList<QPointF>\0\0\0\0\b\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0@\x12\0\0\0\0\0\0@\x10\0\0\0\0\0\0@\x1a\0\0\0\0\0\0@\x18\0\0\0\0\0\0@\"\0\0\0\0\0\0@0\0\0\0\0\0\0@(\0\0\0\0\0\0@B\x80\0\0\0\0\0@,\0\0\0\0\0\0@J\0\0\0\0\0\0@.\0\0\0\0\0\0@R@\0\0\0\0\0@3\0\0\0\0\0\0\0\0\0\0\0\0\0\0)" [spline-pitch] points=@Variant(\0\0\0\x7f\0\0\0\xfQList<QPointF>\0\0\0\0\x5@\b\0\0\0\0\0\0@\x1c\0\0\0\0\0\0@\x1c\0\0\0\0\0\0@Q\0\0\0\0\0\0@%\0\0\0\0\0\0@Z\0\0\0\0\0\0@-\0\0\0\0\0\0@`\x80\0\0\0\0\0@5\x80\0\0\0\0\0@d \0\0\0\0\0) [alt-spline-pitch] points="@Variant(\0\0\0\x7f\0\0\0\xfQList<QPointF>\0\0\0\0\x2@\x1e\0\0\0\0\0\0@,\0\0\0\0\0\0@1\x80\0\0\0\0\0@T@\0\0\0\0\0)" [spline-roll] points="@Variant(\0\0\0\x7f\0\0\0\xfQList<QPointF>\0\0\0\0\x3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0@\x1c\0\0\0\0\0\0@\0\0\0\0\0\0\0@;\0\0\0\0\0\0@U\0\0\0\0\0\0)" [spline-Y] points=@Variant(\0\0\0\x7f\0\0\0\xfQList<QPointF>\0\0\0\0\x2@\x4\0\0\0\0\0\0@\x18\0\0\0\0\0\0@&\0\0\0\0\0\0@:\0\0\0\0\0\0) [spline-X] points=@Variant(\0\0\0\x7f\0\0\0\xfQList<QPointF>\0\0\0\0\x4@\0\0\0\0\0\0\0@\x10\0\0\0\0\0\0@\x14\0\0\0\0\0\0@4\0\0\0\0\0\0@!\0\0\0\0\0\0@D\0\0\0\0\0\0@%\0\0\0\0\0\0@O\x80\0\0\0\0\0) [alt-spline-Z] points=@Variant(\0\0\0\x7f\0\0\0\xfQList<QPointF>\0\0\0\0\a@\x4\0\0\0\0\0\0\0\0\0\0\0\0\0\0@\x14\0\0\0\0\0\0@\b\0\0\0\0\0\0@\"\0\0\0\0\0\0@$\0\0\0\0\0\0@'\0\0\0\0\0\0@4\0\0\0\0\0\0@*\0\0\0\0\0\0@>\0\0\0\0\0\0@.\0\0\0\0\0\0@I\x80\0\0\0\0\0@1\x80\0\0\0\0\0@R\x80\0\0\0\0\0)

Aha!

Problems solved.

Whyever, FacetracknoIR had itself turned to “use Fretrack, hide TrackIR” in the settings. It seemed that BMS is not keen on Freetrack. Turning it back to TrackIR did the trick 🙂

Finally I bought it!
It works great with my laptop’s webcam and shows 29fps even in a darkened room! What’s more, it allows the vJoy sliders to be controlled simultaneously with the TrackIR, defining any segment of any of the 6 tracking axes as an “overlay” for the vJoy, which is very interesting as it gives me the ability to dynamically change the FOV when I reach the maximum allowed travel distance along Z . I can still move my head forward / backward inside the cockpit, and when I get to “full stop”, it starts to zoom in! A very cool feature when working with an MFD and when landing!

@mj3437:

I always link to TrackHat in these discussions. They have everything needed at a good price.
https://www.trackhat.org/

Just that all of their kits with camera are out of stock. And a clip without a high FPS camera doesn’t make that much sense

Delan still sells full kits and at same price range
https://delanengineering.com/shop/

Gesendet von meinem SM-G930F mit Tapatalk

I do think the BMS version makes a difference. I switched to that DLL back with 4.34 and could not make it work. But glad that you are sorted now!

First edition:
https://www.benchmarksims.org/forum/showthread.php?41827-UNOFFICIAL-Running-BMS-on-Linux-WINE-with-opentrack-HOWTO

Any comments welcome.

Thank you sooo much @Vapor, I am finally (after 2 years) able to easily see the position of the Speedbrakes and the Air Source knob!!!

Also, It is now possible to see the highest and lowest parts of the HUD! I could never see the lower part which was a problem when landing at low speed.

This is amazing!!

Thanks Fish, your profile made a difference. Made a few changes to the curves but now I can freeze the view where I want. Excellent stuff, thanks

Just a heads-up: Several users of Opentrack have experienced stuttering recently. It seems to be related to the PS3Eye camera which may have been affected by a Windows update. The problem is that the fps of the camera fluctuates wildly between eg. 2 and 75 fps which leads to jumps in view position and stuttering.

The solution that worked for me and others has been to reinstall the PS3Eye drivers. In my case the drivers were exactly identical to the ones already installed but the process of reinstalling must have made a difference. The fps of the camera is far more steady now.