ca787546

I got the same... the file showing was texture/hook @

I have the exact same issue, except that to add to the problem, every time I select Voice chat on and join a server with Voice Chat, I get a CTD

F4l0, you do great work asking nothing in return for all of us with jetseats, forcefeels, and so on! We appreciate it!

I suggest you look them up on Facebook and write them through there as well. I have had a good experience so far where it comes to customer service, although they need to be a bit better with timing. They do not reply right away, but they do reply.

I don't think it is a software thing because it happens with SimShaker for Aviators AND with SimShaker-Wheels... almost as if after a while the connection drops and re-connects right away. Anyhow, the seat should've arrived by now to Realteus. So far communication has been great, and I am hoping they can either repair it or send me a new one.

Hopefully that has changed :thumbup:

Thanks for the reply Tundra! I'll be sending it back on Sunday/Monday and I am hoping I'll get it back soon :( Have gotten so used to simming with it that I'll really miss the feedback if brought!

Quick question... I have an issue (it has occurred since day one with my ForceFeel). Basically, everything works fine, but every now and then it just shuts off after a while. I have to turn it back on, and restart the SSA service. It has happened with SimShaker-Wheels as well, so I am considering doing RMA on sunday. Has anyone experienced something similar, and if they did, what was it or how did you fix it? Thanks for any help!

I have the ForceFeel and I am satisfied with it. SimShaker Wings doesn't support it yet, but SimShaker for Aviators thanks to the amazing work of its developer, and SimShaker wheels have support for it. To be honest, I don't think there'd be much difference between the JetSeat and the ForceFeel. I think they're both good, just a matter of which one you want to get, price, and which one is in stock. That's my opinion, everyone is entitled to their own.

F4l0! Thanks for the latest beta update! Now the ForceFeel is working! There's still the problem with the effects getting stuck but that's such a minor thing when compared to the fact it wasn't working before! Thank you! Keep up the great work!

Seems I spoke too soon... it's on and off... got it working again a little bit again, but not it's not working anymore. The problem seems to be only with SSA and the SeatHandler.

Ok.. just did a quick test... not sure how but it worked!!! I closed the Seat Handler. Then went to the SSA Install folder/Data, and ran ibaJetseatHandler.exe as administrator. Gave me an error, closed it. Then hit restart on the ForceFeel output mode, and now it works!!! YES! Hope I can keep it working!

I'm sorry, the latest beta keeps giving me the same problem. It says ForceFeel Seat State: Not Connected, then a message that says: "Could not connect to ForceFeel - try to 1) restart the handler application trough the service tab in SimShaker For Aviators or 2) reconnect the seat and restart the handler" I tried both options, to no avail. I even tried a different USB, and restarting the PC and got the same result every time. The ForceFeel Control Center does communicate with the seat and works fine. I also tried SimShaker - Wheels and that was also working successfully. I wish I could give you more data to work with. I'll try more things tomorrow to see if somehow I can get it to work.

I also have this same issue. I have written a bit more detailed message to Olaf about it. I wonder if it's the new ForceFeel DLL? I'm not sure. I try re-installing, re-starting, closing ibaJetSeatHandler, I even tried grabbing the ForceFeel.dll from the ForceFeel Control Center and putting it in the SSA folder as a replacement, but unfortunately to no avail. For now I am back to just using the FF in sound mode which is nowhere as rewarding or immersive as when using the amazing SSA.

I'm getting the same errors as Arctander from SeatHandler. And I am getting nothing from the ForceFeel. Unfortunately the last update seems to have broken things for me. I check with the ForceFeel Control Center and the connection works and all motors are working, but unfortunately I'm getting nothing from SSA when I launch DCS or X-plane.

F4l0!! You and the SSA team, THANK YOU for implementing support for the ForceFeel! had an amazing time with the Tomcat! Please, can you remind us how we can donate to you! If you have a paypal option that would be great! Best regards, Daniel

Thanks for the tip Arctander! and thanks again F4l0!

Also... when I select the ForceFeel in SeatHandler 1.0.0.8 I get another Unhandled exception with the following details: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at ibaJetseatHandler.JetseatHandlerMainForm.InitSeat() at ibaJetseatHandler.JetseatHandlerMainForm.cb_SeatSelection_SelectedIndexChanged(Object sender, EventArgs e) at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e) at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m) at System.Windows.Forms.ComboBox.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- ibaJetseatHandler Assembly Version: 1.0.0.8 Win32 Version: 1.0.0.8 CodeBase: file:///C:/Users/danie/AppData/Local/Apps/2.0/TAJOEV3X.15N/R895Z9VX.K6A/sims..tion_582bdd2a80198c18_0001.0003_2c4a060cdb038281/Data/ibaJetseatHandler.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.7.3353.0 built by: NET472REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. THANKS for any help, sorry for including all the logs!

First of all, THANK YOU F1l0! ForceFeel support!!! Unfortunately, it is not working for me yet! Downloaded version 1.3.6.0, but whenever I run SSA, I get a message from Seat Handler 1.0.0.8 that says: "Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately. Retrieving the COM class factory for component with CLSID {22420DBA-2927-4d71-B6B8-028982A62B72} failed due to the following error: 80040154 Class not registered (Exception from HRESULT:0x80040154" Under details, it shows: "See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {22420DBA-2927-4D71-B6B8-028982A62B72} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). at ibaJetseatHandler.Seat.JetSeat..ctor() at ibaJetseatHandler.JetseatHandlerMainForm.JetseatHandlerMainForm_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- ibaJetseatHandler Assembly Version: 1.0.0.8 Win32 Version: 1.0.0.8 CodeBase: file:///C:/Users/danie/AppData/Local/Apps/2.0/TAJOEV3X.15N/R895Z9VX.K6A/sims..tion_582bdd2a80198c18_0001.0003_2c4a060cdb038281/Data/ibaJetseatHandler.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.7.3353.0 built by: NET472REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box." Anybody has any info on what could be causing this and how I may resolve it? I saw Arctander's earlier post about renaming the copy of ibaVibroEffects to ForceFeelEffects but that did not fix it. Thank you guys if anyone can shed some light on how I may get this working!

Very nice workaround Arctander! I gotta say, it's a complete shame that we still do not have PC mode working with SS-Wings and SS-Aviators. SS-Wheels is finally out of beta and works great, which just makes me want the same support for Flight Sims (since that's what I bought the ForceFeel for primarily!).

The keys for SimShaker Wings that I received from Realteus don't work either. I hope they will work once the ForceFeel option is activated with a beta, like the SimShaker Wheels. On another note. I have communicated with the developers of SimShaker for Aviators and SimShaker Wings/Wheels. Not clear with a date, and they need to work with Realteus to implement support. So Realteus needs to get things rolling for the developers to be able to support the ForceFeel. Also, SS for Aviators is developed by a team that does NOT get paid as far as I know, so they're doing a favour for the community, but as such, they also have a life, family, work, and so on that demands their time ahead of development. That's my understanding, and I'm not quoting anyone here, just sharing my thoughts.

I don't have a JetSeat to compare it to. I tried it with Beta SimShaker Wheels. I know it's not DCS related, but with software support it sure ROCKS. The 8 motors give quite a bit of feedback. Hope SimShaker for Aviators gets support for the ForceFeel soon.

Hi! I really appreciate all the hard work f4l0 has put into creating SimShaker for Aviators. I want to start by saying thank you. I just received my ForceFeel, and I know that there is no support for it yet, but I would like to know if there are plans for support in the future. I'm hopeful there will be. Cheers!

Ok, so a quick and dirty first impressions post: Picked it up from the FEDEX office today. They would've delivered it tomorrow but since I have a flight tomorrow morning and won't be back from that trip for a few days, I decided to just drive there and get it. The packing is satisfactory. It looks like an item you could definitely pick up and buy at a store. The box had some very minor aesthetic damage from transportation, but overall it arrived in almost perfect conditions. So to the unboxing: Inside you will find the manual and a CD in a ziploc bag, the power supply in its own small white box, and then the Forcefeel in a plastic transparent bag. The CD contains 3 pieces of software: ForceFeel Control Center, SimShaker-Wings and SimShaker-Wheels. At the time of me writing this, the only functionality I have used is the ForceFeel Control center and then tried it on DCS as Sound mode, but more on that later. The Manual is about 80 pages, but in reality it is only 10 pages written in 8 languages and it is quite simple and straightforward. The power supply is rated for 100 to 240 volts, so it will work without a transformer anywhere, as long as the plug you ordered is the correct type (it was for me). The biggest concern I have is that the power cord coming from the power supply is far too short. For me it is a bit of a problem that could easily be fixed by either including an extension or providing a longer cable. I literally have to unplug it every time I want to leave my desk, and I consider the powerbar to be relatively close as it sits right at the end of my desk slightly below where my monitor sits at just slightly longer than at arms' length. At first impression, the Forcefeel gives you a sense of good quality materials all around. The straps are a bit light, but more than adequate. Once installed, the seat is comfortable to seat on, although the back bottom motors (3 and 4) do protrude a little bit too much for my liking, but not enough to make me want to remove it from the chair every time. Also, it likely will feel different on different chairs, so results may vary. The physical installation is quite easy, you put it on your chair, 4 motors on the bottom, 4 motors on the back, use the straps to make it steady and stable on the chair (this works remarkably well) and then plug in the power cord to the seat, the USB cable and the audio cable to the PC. The cables also include and audio-in to plug in headsets to the seat, although I have not tested that feature yet. Following that, you install the ForceFeel Control center and turn on the seat with the attached control by pushing it until it lights up and voila, you're good to go... well, sorta. The ForceFeel Control Center doesn't really do much other than let you choose Sound Capture Mode or PC Control Mode, select the strength, and click whether you want to convert 6 to 8 vibration zones. There's a simple massage tab, and you can test each motor independently. You can also change between Sound Capture mode and PC Control Mode using the physical control, as well as adjust the strength by phisically rotating the control. As for the SimShaker-Wings software, at the time of writing, I was unable to make it work. I contacted Andre, the developer of the software. His very prompt response, although courteous, was a bit disappointing. Basically, it is all in Realteus' hands whether SimShaker-Wings support will come in the future or not. Apparently it is coming soon, but has not occurred yet. Andre also added that SimShaker for Aviators (a separate software that is the one required for PC Control Mode to work with DCS, X-plane and Prepar3d and developed by f4l0) currently does NOT support the ForceFeel. SimShaker-Wings does NOT have plans to support those 3 titles either. As a side-note, I did not try SimShaker-Wheels, because when I attempted to install the beta version provided in Andre's Blog, Avast kept detecting Malware. I let the developer know. It may be a false negative but I just did not feel like testing that theory. So, I was only left with Sound Capture mode to try. I had to use a bit of a work-around to make it work. I fly with the Oculus Rift in DCS, and for Sound Capture mode to work, it has to receive audio. So I followed the directions offered here to mirror the sound: https://forums.oculusvr.com/community/discussion/37895/how-to-mirror-audio-on-two-devices-soundcard-and-rift Then I launched DCS, and boom, shaking and rumbling was finally working. The motors are strong. It really gives you a nice feeling of immersion, particularly for the jets. I love how the rumble increases as you speed down the runway and then suddenly stops once you're airborne, just like in a real aircraft. Then came the moment to pull Gs, although you obviously cannot feel the Gs, you definitely can feel the rumble as you increase the angle of attack, and its more pronounced at higher airspeeds. I tried this using the Hornet. Also, the catapult launches do feel nicer with the ForceFeel. On to the choppers. I tried flying the Huey around for a bit, and of course, it was a lot of rumbling, although it definitely did not give me as good a feedback as in the hornet. When you unload the rotor blades, the vibration does feel eerily light, and a bit stronger as you load them up. Having said that, we are just working with sound, so if you were to use a sound mod, the experience would change completely. Having said all of that, it was fun and added to the immersion. Finally, the P51D and the Spitfire had a go. The ForceFeel really makes sure you feel the rumble of those old piston engines firing away in front of you. In the P51D with its laminar airflow wing, you could really feel as you approached the critical angle of attack and it was rewarding to open up on that Fw190 in my sights and sense the vibration of the guns. In conclusion, the ForceFeel is a REALLY nice piece of hardware. At the time of me writing this, on day one, I really feel that it could be exponentially better if only they added better software support. I want to be able to feel the engines because they're engines, not because they make a low rumble. I have no experience with the JetSeat, but I am now very curious to compare experiences. The quality of the seat itself is great, and except for the short power cord, I see no shortcomings in hardware. The only problem I see on day one is the software support. I really hope it gets sorted out and FAST.

At this moment, I cannot get it work in PC mode, only in Sound Mode... hope that changes soon because I bought this mostly to use with DCS, X-plane and flight sims but the output option for ForceFeel is NOT available in SimShaker Wings or SimShaker Wheels. I wrote to Realteus about this already.