Arctander

After restart I Also tried a quick flight in an F18. As soon as I pulled G/caused turbulence the effect got stuck. I can report however that all eight motors were vibrating for me.... Is it possible that the seat gets stuck with an effect it then blocks all following signals? Or could it be a 'disconnect' that leaves the last effect playing? Is there any way of seeing a log?

No change for me. On test mode the 5th motor keeps running and won't stop requiring physical shut down of the seat. Edit: If I close and restart SSA I get this error from the seat handler: https://imgur.com/K4Qq2KX Then this one https://imgur.com/VPwmSni

That’s good to hear!

I don’t know i’m afraid.

When you get that error there should be a green icon in your task tray. It is the seat handler 1.0.0.8. On it there is a drop down box to select the force feel seat. See if that fixes it.

No you don’t. And in fact if you run it before running SSA I understand that it can stop SSA from ‘talking’ to the Forcefeel.

Hi Andre - do you make the Jetseat FSE yourself? If so - is there any chance of a custom request (add an extra shorter strap at the front to go around a joystick mount to keep the pad from being slid backwards). Also what is the benefit of the FSE vs the normal 901 that makes it worth an 8 week wait?

@Goshe - for DCS you only need Ss Aviator (beta)

Apologies for the confusion - My issue is that the seat gets ‘stuck’ in that continuous effects often don’t stop. So say I pop out my speed brake in an f18. The seat vibrates. I put the speed brake away and the seat continues to vibrate - and because it is doing so - no other effects will play (like weapon release, gear, flaps, touch down etc) If it is doing that because of a hardware fault and not due to the ongoing software implementation that you needed more information form Realteus to solve I need to return it. No one else I have seen have reported it, I just got a little confused as you said you had raised it with Realteus which would not be needed if it was a hardware fault.

Hardware problem as in defective motor? (The fact it is the same motor each time during the test makes me think so...). If there is no software fix planned/possible for this please just say so I can contact Realteus and either get a replacement or refund.

Yes - even from a cold start. For clarity - cold start - no vibration. Jet turns on, I fly, vibration gets 'stuck', I land, go back to cold and dark, seat still vibrating. If I use the force feel control app test function - each motor turns on and off at will, but if I use the SSA test function the lower left back motor seems to get stuck.

Does anyone with a FF seat get 'continued' vibration even when you shouldn't? I'm getting quite a few effects persist (on SSA beta 1.3.6.6). Things like speed brake shudder, afterburner etc on the F18 just continue even when they shouldn't.

Hi f410, I've been doing some further testing and I've turned off lots of effects - yet I'm still getting continued vibration. What I think may be happening is any effect that is 'time bound' - such as weapon release, gear down etc is fine. However any effect that is 'continuous' until the situation that caused it to start stops, has a chance of not in fact stopping when told to. So things like WEP/Afterburner, Speed brake shudders, gfeeling effect - all of those can cause continued vibe even when the state that caused it to start has stopped as the 'stop' commands aren't always being acted upon by the seat motors. If I remove all of these 'continued' effects - then the discrete effects come through absolutely fine... It's a real shame as the discrete effects are so cool.... I've also noted that when using the 'test' funtionality - over 50% of the time - the lower left back motor gets 'stuck'. Do any other Force Feel users also feel this? It works fine on sound mode as far as I can tell - and the force feel app test seems fine too (Note - I do not use it when using SSA).

Amazing isn’t it!

I unchecked each in turn to try and isolate it. Removed Ground roll - issue remained. Removed Whee Blocking - issue was fixed. Did not remove ground bumps. Once I landed and turned off the engines the vibration ceased, F/A-18C was what I was flying.

Are you on the beta version of SSA? You need to be for F14 support atm...

Here: http://dsteam.azurewebsites.net/SSA/beta/publish.htm

I also have this problem using kneeboard builder. Folder name for me was F14 as well

Can confirm! :-) Just fixed mine too! And I'm a normal non-electronic whiz. It's fiddly though! Luckily I have one of these for my modelling: https://www.amazon.co.uk/Fityle-Auxiliary-Magnifier-Magnifying-Embroidery/dp/B07KCWR8Z7/ref=sr_1_10?ie=UTF8&qid=1552639624&sr=8-10&keywords=modelling+magnifier+and+stand Made it SO much easier!

Hi f410. Took my first flight on my Forcefeel this morning and it felt amazing to start! Ground bumps, flap effects etc were coming through cleanly. After take off at some point I realised however that it appeared that the effects got 'stuck' at some point. I'll do some further testing to try and nail down which it effect it is, however doing some testing afterwards using the massage and test functions I have noted for the massage function it also gets 'stuck' on the front two on the legs. Pressing stop in software has no effect. When SSA is closed the effect persists. You have to turn off the FF using the physical button to stop it. Then when you open SSA again it won't play effects (either test or massage or in plane). You have to restart the computer to make the connection again. I will try and nail down which 'flight' effect it got stuck on. F/A-18c was the plane I was flying at the time if that help. This was irrespective of if the Jetseat control handler was installed or not (I am on beta 1.3.6.6)

As others have said. No. But what you can do is intelligent use of the recenter button if it is that much of an issue for you. Look to 3 o’clock. Recenter. Looks to 9 o’clock. Congratulations - you’re now looking behind you. Look forwards. Recenter.

Oh boy oh boy oh boy.... i’n Stuck at work but will jump in my simpit as soon as I get home to test!

http://dsteam.azurewebsites.net/SSA/beta/publish.htm

That’s how I got past the error in question.

Hi f410 - the massage function and test function in SSA didn’t output any vibrations. The one in the Forcefeel control center did... Correction! Just tried again - when the massage function in SSA is enabled, the front two vibe motors (1 and 2) run. Clicking 'stop' doesn't stop them. I have to power off/on the FF to make it stop.