hexpod 6-dof for Simtools

I would say so:
Whatever the heave-offset you want to use, after you change it, you always have to bring the AMC bit "Signal Output" to 50% using "Field Orientation" slider.

After having done this on the software side, you look at the angular orientation of your levers, and you turn manually your sensors so your physical levers match this value.

I you have trouble, PM me your config file.

I don't know what 'bring the AMC bit "Signal Output" to 50% using "Field Orientation" slider' means but I might be able to figure it out.

It's probably something dumb I'm missing but I'm stuck on Step 6:
6. in "SimTools - Game Engine" under "Axis Assignments" choose "AMC heXpod" as "Axis Type"

I spent nearly two hours doing google searches etc. , I'm sorry to have to ask.

There is no such option, see attached image. I have tried with both Default and DCS profile, and DCS and no limits. Makes no difference.

PS- Also, there appears to be one instruction for X-Sim (not simtools) randomly mixed in?
"Be aware: to establish the connection between heXpod.exe and X-Sim, copy the x-sim 6DOF.dll file into: "\X-Sim\Interfaceplugins" folder"
I did everything I could to confirm that this instruction was not for Simtools users, there is no such folder in which to place 6DOF.dll

If there is no HexPod option in that dropdown you have NOT installed the HexPod plugin that comes with the HexPod app. You have to drag the plugin on top of the plugin installer.

And then for ongoing updates, follow the instructions #2 of the readme. Someone should update that doc clearly and I’m happy to take a look.

“2.) PLEASE UPDATE THE "AMCHexpod_InterfacePlugin.dll" THROUGH "SimTools_PluginUpdater.exe" for future releases.

I did install the plugin via click and drag to the plugins installer, I even did it a second time to be safe. I got a message both times that it was installed successfully. @Psionic001 on what version of SimTools did you confirm the HeXpod option present in the dropdown? I'm on 2.3.1 I think.

Just to make sure we are on the same page, I do have heXpod in the dropdown for interface, just not in the dropdown for Axis Type. Hexpod told me to just use normal or advanced, he has been very responsive and helpful. =)

When I was going back and forth testing the latest test version of simtools, I did lose Hexpod from the Axis Type at one time and needed to do a full uninstall(remove all files)/install to fix. Don't know if that will also help you?

Hmm... I may try that. Thanks for the head's up!

@Psionic001 I have uninstalled Simtools completely twice now, and installed the RC for 2.4 and then used the plugin updater with Hexpod's .dll and got success message but still only have 2D advanced, 2d standard, and 2d basic in the dropdown.

It works, but does this mean I'm not getting access to the heXpod specific filters?

Start to listen and stop spamming the forum. I told you to use standard assignments.
.dll is for the heXpod INTERFACE

The heXpod assignments were only for labeling clarity. As smoothing and washout from 2.3.1 was not quite “orthodox” I wouldn’t recommend to use it until it gets updated for 2.4.

For any beta and experimental feedback, talk directly to the developers

I am listening @hexpod . =) And it's not spam, I was only responding to the messages of those who were trying to help. I know I've been a pain in the butt with my unorthodox dimensions and such, so no worries my friend!

If you read all the posts above you will see that I asked about it while it was late at night in Europe hoping someone could tell me how to fix it without having to wait for you to get up in the morning. While you were asleep Psionic001 told me that if there was no heXpod option in the axis assignment dropdown I had done something wrong. In the morning you told me by email that it was unnecessary to follow step 6 in your readme.txt instructions, so in the very next post I stated that you had told me to use the generic assignments (which is what what I've been doing) but you never specified whether this was a change and your readme was out of date, or if using the generic assignments was a temporary workaround. After that Seattime told me he had a similar problem and suggested something he thought I should try and I thanked him. That's all!

No spam, just folks trying to help one another out. =)

To keep a bit order into it, you may not start to combine and mix up simtools 2.3 with simtools 2.4 beta plan.
Simtools 2.4 will be a quiet new experience.
Taking part in a private beta testing, in order to avoid confusion with the users which are not beta testers, I advise you turn your questions and suggestions directly to developers.

Understood. Wilco.

@hexpod I am unable to get the max heave out of my platform using HexPod 2.7 even when the game is maxing 100% heave.
When I move the slider manually, I see that the travel is allowable and within limits.
Please see these screen grabs as to how I'm even trying to force excessive heave but the sliders only move a short part of the range.
It feels like HexPod app has some other limiting filter when seeing the game data.

This heave via the game only moves 68mm up, but you can see the game is outputting 100% of axis used.



This shows the manual slider allows 196mm of upwards travel.

Axis3a corresponds to heXpod heave slider. It seems fine.
The reasons why you see the discrepancy between Heave and Axis3a could be:

1.)
- you use axis limiting below 100 in axis assignments
2.)
- you use the percentage below 100
3.)
- you use SimTools washout

If you use SimTools smoothing with SimTools washout, in some circumstances it can reduce your axis range.

I was asking plenty of times to add an axis gain in the filtering or to increase instead of decrease the percentage of the axis in the assignments. (It went from 150 to 100 between 2.3 and 2.4.)

Having more important stuff to fix, it seems @yobuddy forgot to add the gain or doesn’t want to add it for some reasons.

To compensate, you can empirically judge how much it eats and increase the limit axis intensity in heXpod. Shitty solution but should help.

@Psionic001
IMHO it’s a missing feature. If there is many requests for it, maybe you can hope for a 2.4.1.
Talk to @yobuddy

OK good solution. I see you aren now understanding my questions about this. I'll see how it behaves and report back.

@hexpod
Thanks, I checked your thoughts on why there would be less movement and the axis limiting had been set to 50 which looks like a the cause to me.