jjohnson241

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.

Hi, Been awhile since I've flown the Sabre and I noticed a problem. At low altitude and above app. 550 knots, the plane rolls left without control input. The roll can be corrected with trim but is strong enough to require significant trim or stick input to correct. I noticed this both in DCS 2.1 and 1.5. I fly with a Warthog, no curves or dead spots configured. I don't recall this behavior but as I said it's been a while since flying the F-86. All flights have been off-line. The high speed non-induced roll is certainly a bummer in a dogfight. Has anyone else noticed this? Thanks.

Congratulations. The P-51 is a handfull to learn and there's no sub for practice and proper procedure as you now know. Keep at it and you'll get there.

Yes, it's a cross wind and it can be changed in the Mission Editor to zero or whatever value you want and from whatever direction. Open the mission in the ME and click on the "Weather" button on the left side tool bar. you'll see wind velocity and direction for three elevations on the Weather block that opens in the left.. I believe they are 20M, 2000M and 8000M. You should see 4m/sec for the 20M entry. Change that to 1M/sec. You open the ME from the menu on the right side of the main splash screen. When it opens, you'll see the NTTR map. There is a tool bar on top. The leftmost button is Open. That will give you a menu (directory) that depicts the missions. The P-51D entry is on the left side. highlight that and in the right pane will be a directory. Select "Quickstart" and the p-51D Landing mission. That will load the mission. Problems, read the manual under Docs in the DCS World Alpha directory. Edit: I just looked at the mission that BIGNEWEY posted here for you and it has zero wind. So, if your drifting right on your approach in that mission, it's because your not correcting for torque taking the plane to the right.

I can't offer you any tips because I'm totally confused regarding the problem your having and "what you're thinking about doing". If the repair didn't solve whatever it is, then I'm at a loss. Big stick is delete the installation and reinstall. Edit: I went back and looked at your original post and the screenshots. The Map is not moving. Your plane is drifting right. You need to continually trim and correct the line of flight of a prop plane as you decrease speed. Look at the landing tutorials posted here and on U-tube. It looks to me that there is a cross wind or quartering wind that is taking you off course. All it takes is a mild wind to do that. I looked at the landing mission in the ME and there is a 4M/second wind blowing to the East 20M above ground level. That's more than enough to cause your plane to drift to the right at low power settings and at low altitude. The TF-51 is the same animal in this respect. No mystery, wind is causing you to drift to the right and off line from the runway. The earth is not moving.

Well that's a long shot but if you want to repair the DCS Alpha NTTR copy, just go the your start menu, all apps, Eagle Dynamics, and select/run "Repair DCS World 2 OpenAlpha". The installation will detect whatever files have been altered from "stock" and download/replace them. Just curious, what graphics enhancer did you install?

BIGNEWEY + Chuck, I was able to play the track and take control and land successfully. I did this without the "Sync controls with HOTAS" enabled, my normal setting has this disabled. Chuck, until you supply a control input such as throttle, gear down, etc., the plane will just drift to the right (due to torque I guess) and nose into the ground. You need to provide some kind of control input before you "lose" the plane. Again, with no control input, the plane would "appear" to drift to the right of the line to the runway. Are you sure you have the control axis set correctly? Can you control the plane at all (throttle, pitch, roll, etc?) I don't know what to tell you other than check your control settings, particularly the axis settings, and let us know.