jjohnson241

Skull, I have your Mod installed in both the Stable and OpenBeta release of 1.5.4. No problem. But, I modified your JSGME file structure to begin with the Mods folder, not the Eagle Dynamics/DCS World path. I had to do that to install the mod in the correct path. I believe that is Chief's problem. Restructure the path in the JSGME to Mods/Aircraft/... not Eagle Dynamics/DCS World/Mods.... and you'll be OK.

The F-86 has the same type of "hold and go" system. Took me awhile to get used to that also.

I too had no TIR movement in the aircraft listed above (I don't own the Gazelle) in both the BETA and Stable releases. I had to delete the aircraft from Config/Input in Saved Games then reassign the controller options. I don't know what's causing the TIR problem but I had the same thing happen after the last update to 1.5.4. Is the fact that these aircraft have not been updated to the new TIR setup causing this problem?

Despite several searches I can't find the 1.5.4 TrackIR Behavior thread. Can someone provide a link to that thread? Thanks Edit: Please disregard, I found the thread.

+1

I have an A-10C profile in my TIR titles and it activates a hen I fly the A -10C. I adjusted the view center in that profile and it worked. The Profile may have been a residual from the old stand-alone A-10C but I know I didn't create the profile. It works and that's all that matters. Hi

I played around with each plane I have (I have all except the Gazelle) and here's what I did for the A-10C: I'm sure you guys know that TIR has included a profile for the A10C. Just look in the "Titles" tab in the TIR software for DCS: A-10C. Using that profile, I just re-centered the view upward 22 degrees, saved the profile and voila! good to go in the A-10C like nothing had changed. The remainder of the planes are livable with the TIR change in 1.5.4. In some cases in may look a little different but all are flyable. I don't really understand what and why the change was made, you know if it ain't broke...., but I guess I can live with it. :joystick:

Thanks for the clarification. I thought it meant corrected the TIR problem that was created by last weeks OB update and repeated today. I missed your 1.5.3 reference.

+1 From the Changelog: "In-cockpit TrackIR functionality corrected. Influence of mouse and default camera position was switched off." Corrected? I hope the party that made these changes has the benefit of feedback from this forum.

That's your opinion Ace, and you're welcome to it.

Thanks, that was my guess. I made a JSGME enabled Mod and tried it out. Worked fine. Thanks again.

What's the syntax of the time values that would be increased? Can you give us an example, possibly time xxx.yyyy change to aaa.bbbb? Thanks.

The folder name of the Mod differs, that's the reason I asked. Thanks.

I assume we remove V1 of the Caucasus map from JSGME?

Good Job, Starway!! Now let's hear those updates on Goal 2 :thumbup::thumbup:

Hi Starway, Congratulations on reaching your first goal. Many of us are frequently looking at this thread for progress updates. So, a suggestion: Pick a schedule by which you'll post updates on the donation amounts you receive and publish it here. Something like "beginning 1700hr CEST and every x hours thereafter, the first post in this thread will be updated with the donation amounts received". There's enough interest here that such a schedule would be very well received. Thanks.

I'm in. Suggestion though, you may want to include a link to the English speaking PayPal site. I don't speak German and had to go to the English PayPal site to donate. No big thing but it might turn some off.

Considering a donation. Can someone explain the difference between the T3 and T4 versions of the mod? Thanks.

OK, then ED males the decision that they don't want my money. I guess the fact that SweetFX does not modify the SIM escapes them.

So would I. I've used SweetFX and of late SweetFX with Reshade for several years without problem. I've got it running in all three installations (Public, Beta and Alpha) of DCS currently. I'm aware of the problems with DLC campaigns and I'm of the understanding that the campaigns use a DRM scheme written specifically for the campaigns. I don't understand why this DRM scheme has a problem with SweetFX/Reshade as SweetFX is a post-processor and doesn't alter game code nor execution. It simply enhances the video out of the game as it is delivered to the graphics processor. Others here (Yo Yo for example) have questioned the incompatibility brought about by the DLC DRM as being harmful to the success of the DLC products by excluding the purchase of the DLC by the DCS SweetFX user. I have not purchased any DLC campaign that conflicts with SweetFX. Apparently ED is not concerned with the problem nor resolving the conflict. I've seen opinions here that the conflict is a SweetFX issue to resolve. SweetFX runs successfully for a myriad of games without issue. I believe it is ED's DRM that's creating the conflict.

OK, thanks.

That update was dated 4-1-16 and I applied the update. Dates don't jive. ??

Hi all, I just installed an update ,1.5.3.52018, to both BETA and Public copies of 1.5.3. Anyone know what's in this update? Nothing posted by DCS.

It's coming along nicely. Please, when the final PDF is created, make sure you use a TOC that contains document links to text. Any manual of this size is very hard to navigate without a dynamic TOC. Thanks.

Thanks for the responses, gents. As I said, it had been awhile since I was in the Sabre and was surprised by the behavior.