Bob1943

Thanks, I will check it out.

Where do you buy the springs from? How hard to install? I also have a CH FighterStick with an extremely light touch. I will try that as well and see if the lighter touch improves the AAR experience in the F-16.

I use the stock Warthog spring and no extension. The structural design of my cockpit will not accommodate a stick extension, without some significant re-design. I am thinking part of the problem may be "auto-trim" in the F-16. I prefer manual trim, but I am from the Century Series era.

Hopefully, that will help with the F-16 air-to-air refueling as well. It has been a real challenge trying to refuel that plane with the Warthog stick. I have been trying all sorts of different curvature settings to get some stability in AAR with the F-16. Although part of that problem is working off of a 2D computer monitor that does not provide all the "real world" peripheral vision in a real cockpit that gives an exponentially better position reference to the horizon and the tanker.

Great pictures. I landed there in an F-100 in September 1970 when we were deploying our F-100s from Phan Rang AB back to the States. I lost my primary hydraulic system about 3 hours out from Vietnam and had to use my Emergency Blow-Down system to get the gear down before landing. I was the last plane to land that day and they had the fire trucks along the runway as I touched down, just in case the gear collapsed. Maybe you were there in the helicopter as well.

In doing a little research, this seems to be common complaint with the F-16 module. Trying to get this plane to roll with the Warthog stick is like stirring molasses. As some have suggested, I have adjusted my axis curvature to -30 degrees and that made a noticeable improvement in pitch and roll rates. Have there been any other "fixes" for this problem besides adjusting the axis curvature values?

I give a brief discussion of our interaction with the Forward Air Controllers (FAC) on page 11 in the Phan Rang article. If a FAC was involved in our mission, we would be given a radio frequency (as part of our pre-flight briefing) on which to contact the FAC. We would usually switch over to this frequency about 50 miles from the target area and begin talking to the FAC to get visual cues (hills, rivers, etc.) to help us locate him and the target area. He would be looking up for us and we would be looking down for him. Once we had made a successful rendezvous, he would give us some target info and confirm the ordinance that we were carrying. He would specify the order in which he wanted the ordinance dropped. Unless there were some obvious ground references for the target location, the FAC would usually fire a smoke rocket towards the target and then give us drop instructions relative to that smoke, e.g., "50 meters east of my smoke". If friendly ground troops were involved, they would usually pop smoke as well to identify their position. Before rolling in, we would have to confirm that we had both the smoke and FAC in sight. He would then clear us in hot. At that point we would make sure the sight was uncaged with the correct mil depression dialed in, arm the appropriate wing pylon stations and call "In hot". The FAC would then say "Have you in sight, Cleared hot". After each ordinance impact, the FAC would radio an estimate of where we hit relative to the intended target, e.g., he might say "Blade 2, hit 20 meters south of leader's impact". We always flew circular patterns around the target, keeping the FAC in sight at all times, although he was usually at a much lower altitude than we were. During our ordinance deliveries, we always flew the curvilinear approach, only rolling wings level for a second or two before hitting the pickle button. Then it was "jink right - jink left", etc. coming off the target. We never flew a straight line, especially during low-level drops like napalm and high-drag bombs. http://theseverts.com/Phan%20Rang%20News%20207.pdf

Yep, been there, done that in 1970 in the F-100. http://theseverts.com/Phan%20Rang%20News%20207.pdf

For the benefit of anyone else who might encounter the Windows "CLR Error 80004005", here is a short description I found this morning when Goggling that error code: "One of the most common CLR errors is "CLR Error 80004005," which occurs on Windows systems during the start-up process. This error is generally caused by having more than one .NET framework installed on the system at one time. While two or more .NET frameworks can work simultaneously on a system, some have compatibility issues. To resolve a CLR error, the multiple frameworks must be uninstalled and reinstalled correctly." There are numerous articles on this error code published on the Internet. I have been reading through several of them this morning in an effort to become more educated on this issue. Hopefully, with some more reading & thought, I will get the confidence to give one of the published solutions a try in the weeks to come. Again, this error code is solely generated by a glitch with the Windows Operating System, it is not being generated by any problem with the SimShaker software. Andre and f410 were exactly correct in their previous assessments of this error code.

Andre, I am not inferring that this is your issue to fix. Sorry if I gave that impression. I now fully acknowledge that this is an issue with the Windows OS, not with your software. I do not have the skills to comfortably experiment with repairs to the Windows OS, I would most likely cause more problems than I would fix. Yes, I could pay $150 to $200 to take it to a computer repair shop and hope that they could fix it without having to deal with re-installing all the 3rd party apps. I don't have the budget to do that right now. So I accept the situation until I can find a workable solution in the future. Again, my apologies if you were offended by my comments, no intent there on my part. Your SimShaker software is a great asset to the flight sim community. Update: Oct. 12, 2020: I have spent the past few days trying online suggestions for fixing the "CLR error 80004005" issue - none of them worked. Also spent a couple hours with tech support from the company that built my computer. They tried everything short of a Windows 10 Reset, with no success. Even Microsoft tech support was unable to offer a workable solution. So, it appears that the only solution to this error (in Windows10) will be a Windows10 "Reset/Refresh". The downside to that solution is that all my apps get removed from the computer during that process. Not looking forward to going through the re-installation and license deactivation/reactivation process for all the apps. I will hold off on that "last resort" solution in hopes that a future WIN10 update might fix the problem. Microsoft seems to have embedded the .Net Framework code into Windows 10 in a manner that prevents anyone from getting to it to do repairs. It was more accessible in previous versions of Windows.

I will try a WIN10 Refresh and see what happens. Although I have never attempted this operation before, it sounds pretty straight-forward. I will report back. Update: After reading more detail about the Windows 10 Refresh operation, it appears that it will delete all my 3rd party apps that have not been purchased through the Microsoft store. That is not something that I want to deal with, i.e., re-installing all those apps and trying to find all the required license information. Plus, there is no assurance that the Refresh procedure will fix the problem. Also concerned that it might somehow cause issues with my installed Microsoft Office products and professional business files linked to those applications. I have never performed a WIN10 Restore Point on this computer, so restoring to a previous point is not an option. Still very puzzling as to how WIN10 could have gotten corrupted to prevent SSSM from running. With all the SSA/SSSM users around, it is also surprising that no one else has ever encountered/reported this fatal Windows OS error.

I Uninstalled both SSA and SSSM and then did a fresh install of both programs. Upon running the new installed versions, I get the same fatal error message for SSSM. This is really unfortunate. I have $360 invested in new amp and bass shaker hardware that appear useless at this point. It is odd that everything worked fine one day and then 24-hours later I get a fatal error message when trying to run SSA and SSSM. My WIN10 OS is up to date with the latest version, including .NET 4.7.1. Computer is only 1 year old. Anyone else have any suggestions?

Using Windows 10 Home, Ver. 2004 with .Net 4.7.1

For unknown reasons, I now get this error message everytime I start SimSkaker for Aviators. No vibration effects anymore. The error message relates to the SimShaker Sound Module. Up to now every thing has been working fine. Using an external dedicated USB sound module with 2 Aurasound bass shakers. Any suggestions?

Assuming you have a HOTAS setup, there is no need to use a keyboard for switching views, i.e., just bind them to a multi-point of view switch on your stick. That has always worked fine for me. However, I am sure the TrackIR users prefer their method, depends on what you get used to.

Wow, that is a lot of add-on charges for an Amazon product price of $69.99.

I think you would be unhappy with a 2 monitor setup that will divide your cockpit view/HUD between 2 screens, even with a thin monitor bezel. That vertical screen split would bother me. I decided against a 2-monitor setup and bought a curved 34" 1440P monitor, which gives me about a 32" horizontal screen measurement, roughly equivalent to dual 20/21" (diagonal measurement) monitors.

I have an i7-9700K and a 2070 Super and pretty much run DCS at Max settings on a 1440P monitor and usually get well over 60 fps. I have Anisotropic filtering OFF and MSAA set at 2x. Anisotropic filtering was a significant FPS killer for my system.

I am the one who made those posts on the speedbrake files. I also have two 50 watt Aura bass shakers ( as I mentioned in my posts), and I can now feel the speedbrakes with the custom files that Andre provided. I am using a Dayton Audio 200 watt bass shaker stereo amp. Do you have your amp turned up high enough? Also, have you increased the speedbrake "Effects" to 100% in SSA?

I was getting a similar error a few weeks. Check Post 1502 at https://forums.eagle.ru/showthread.php?t=144060&page=151 along with Andre's response at Post 1504. Worked for me. However, your Error message is a little different, but both start with "Unhandled exception".

You will enjoy that 34" Alienware panel.

Excellent, thank you for the clarification.

Andre, if we have a SpeedBrake file in both the Base>2 folder and Customised>2 folder, how does SSA/SSSM know which one to use?

Thanks for the information.

I use the Sony "Sound Forge" software for audio editing. So, that should also work to edit Andre's wav files. Andre, In order to make the wav files more noticeable, are you just increasing the wav file Volume level in your audio editor? Also, for the 3 custom files that you provided, do I leave those in the Documents>SimShaker Sound Module samples>Customised>2 folder, or move them to the Base>2 folder?