Chief1942

Sorry. I apologize for you having to hand lead me through this process, but once I learn it I will not forget it. Thanks. Log attached. dcs.zip

I think this newest Microsoft Anniversary Update is reflective of some of the difficulties ED has when they do an update. There are so many different systems out there one can almost count on the fact that such an update will only create problems for some users. I initially early updated to the Anniversary Update and immediately noticed the problems I spoke about in my previous post. But after reading on here all those that updated without issues, I thought I would give another try. Tried via the regular Windows Update approach, same issues....rolled back. Then tried the recommended Microsoft Media Creation Tool, same issues.......rolled back. That's 3 attempts at the new Update and all approaches left the same issues. " If the dog bites you once....." Now I will listen to the wise sages that have all along said..WAIT until they have squashed ALL the bugs! I am waiting.

Thanks for checking. Thanks BIGNEWY, The problem showed up on one of the updates past, then it appeared to be fixed as stated in the last update. :thumbup:And I didn't see the messages at all after updating. Then went to fly a mission and there it was again.:helpsmilie: Not sure whats up. Tried to attach the log.txt file but keep getting an error. Any advice?:book:

DCS 1.5.4.55584 Update 3 The Museum Relic (MiG-15 and F-86F) campaign release! DCS World Multiplayer. Improved aircraft motion algorithms. TrackIR input data separated to own cpp, cockpit will use angles from trackIR directly (like in old way). Removed “headtracking disabled” message. Artifacts on Maverick's IR-view and Shkval view fixed Input chat commands moved to UI layer Trim will working when secondary FFB device connected Module manager. Added DRM controller for campaigns Su-25T. Incorrect Mechanical Devices Indicator fixed Su-25T. Updated Chinese version of the Georgian Oil War campaign I still get that message at the top right of my screen. Is there a way to get rid of it ?

Engine running or not? As Art-J indicated, one has to have hydraulic pressure to the system for the Parking Brake to set. If you think about it, if the plane is NOT under power, there would probably be little need for a parking brake (they use chocks for that). Totally different when power is instantly available while the engine is running. I will be the first to admit I AM NOT that into the very technical stuff with any of the DCSW aircraft. I tend to focus on the correct operation of the systems without trying to understand the why's and wherefores of that operation.:pilotfly: But for the "purist" I understand the desire to know it all.:thumbup:

Works fine for me. Apply the brakes, pull out the yellow Parking brake handle, release the brakes and the handle stays out (brakes engaged). I have not run up the engine to test how much holding power those brakes have however.

Okay, just for giggles.:music_whistling: I few the F-86 Ground Attack mission and landed at Kobuleti. I went in ahead of my wingman and since, from having flown this mission to shut down before, I knew which HAS he would go to and it would open and in he would go. But we know this only works for AI aircraft as the HAS doors will not open for the "Player" aircraft:(. I went in front of the HAS he uses and waited for him to arrive. When he got close to the HAS the doors opened and in I went, and shut down.:thumbup: He on the other hand, turned around and taxied all the way back to the first HAS one comes to after exiting the far end of the runway. He turned into that HAS and went right through the unopened doors and disappeared.:megalol: Is this issue a Belsimtek thing or ED's? I know there have been discussions regarding the AI and their HAS before and understood that only AI could actually go into those shelters. This is NOT a big issue just thought I would experiment and see what happened.:joystick: Also noticed that as the AI aircraft taxied back to the first HAS, the grass in the landscaping along the taxiways kept fading in and out. One of those issues I suppose that if we just follow regular procedures, these things don't happen, but did think it was interesting finding out just for fun.:D

Put it on 3 days ago, and took it off due to too many small, irritating issues with the Windows part. No issues with DCSW that I could ascertain. Will NOT install the Anniversary Update when it tries via Windows update. "If it ain't broke, don't fix it!!"

Thanks ! Appreciate you examining this . It is not a deal killer as it occurs as the very LAST thing in the shutdown process, so it doesn't have any effect otherwise. And I am not a member of the beta team.

Not sure if this helps. This is a track I did in an effort to provide you some feedback on the P-51 Mustang gear doors "feedback" when they reach full open. It only gives the JetSeat feedback once they are fully down and it continues until I exit the flight. Excuse the flying as I was mainly focused on getting this to work. Gear doors feedback.trk

I have a TitanX current iteration, not the Pascal, but as I understand it, you will have to acquire it directly from NVIDIA. And cichlidfan is correct in that SLI is a waste of money and resources for DCSW. I know I had an SLI setup and actually got better performance once I went back to one graphics card. Good luck in whatever approach you decide on. As to brand, I have always been partial to ASUS but then that is an individual thing based on experience.

Have not ever posted a track, but I will make an attempt and probably learn something in the process. Stand by.

Yes, It is a mod that I came by via Skulleaders cockpit mod. If you go to the first post on this thread Skulleader linked to the mod. I had completely forgotten about it primarily due to it's location after it's installed. Like I found out, it is actually in the "Liveries" file within the mods-aircraft-P-51D=Liveries folder. Never would have thought to look there for a cockpit texture issue. Oh well, onward an upward. And by the way, Semper Fi! Bro. 3rd Marine Air Wing 1960-1964

Finally!! Whoopie!! I got it!:cheer3nc: Seems I have Mudspikes Mod "Vivid Colors" in my DCS World\Mods\aircraft\P-51D\Liveries\Cockpit_P-51D\ plus I had selected it under "Options" "Special" P-51D, "Select a customized cockpit" in the GUI. I had checked the "vivid colors".:doh: Now when I select the "Default" cockpit, Skulls mod is working correctly.:worthy: Never would have thought to look in P-51D Liveries\Cockpit_P-51D. Now to go wipe the egg off my face once more.:bash: I also changed the "Vivid Colors" .bmp/dds to the one that Skull provided and now I have the correct pad color whether I select either "Vivid colors" or "Default" in the GUI. Happy now!

Davison, No other interior mods for the P-51D. I even removed every other JSGME mod except "Skull P-51D last version for 1.5.4" to make certain there were no conflicts with another mod. Same issue, black pad. Yes I opened the Zip in both the installs (_Mods and Mods-aircraft, etc) and checked the p51d-cpt01.bmp.dds and they all show the brown pad, which is the correct color. Here is my file path for the JSGME folder: H:\ DCS World\_Mods\Skull P-51D last version for 1.5.4\Mods\aircraft\P-51D\Cockpit\Textures\7Z P-51D-CPT-TEXTURES My file path for DCS Cockpit for P-51D:H:\DCS World\Mods\aircraft\P-51D\Cockpit\Textures\7Z P-51D-CPT-TEXTURES I do not have any other folders present in either of those file paths for the P-51D cockpit. And every other JSGME mod that I have in the Final Release install works fine. My JSGME file and paths for both my Beta install and my Alpha (Skulls earlier version) install are working fine and have the correct color pad (brown), but using the very same JSGME file path and mod of Skulleaders in my Final Release gives me the incorrect pad color every time (black). Every other aspect of his cockpit mod is all there and correctly displayed. No texture anomalies. As I've said, I thought it was a wrong .bmp \dds file which contains the pad, but it shows clearly the correct pad color in every iteration of Skulls mod that I have on my computer, but simply will not display that correct color once in the cockpit of the P-51D in the Final Release. I really don't know where to go from here and I do appreciate everyone trying to help me figure out the issue. This is frustrating not because I can't live with the pad being black, I can, it's simply I want to know why this issue is occurring. Call it morbid curiosity, but it is beginning to become an obsession now. And I certainly am familiar with these types of issues turning out to be something very simple but overlooked. I've had egg on my face due to that error more than once. Be certain that if I DO find the solution, I will certainly post that here on this thread. Thanks.

Gratitude! You know, I look at those renderings and I harken back to what we thought was great back in the late '90's.:cry: My gratitude for what ED is doing on behalf of such a small niche market, is beyond words.:thumbup: A simple thank you just seems to fall way, way short in consideration for how they are providing for "the few" who still cling to their fight sim fantasies.:pilotfly: I suggest that patience on our part would be the best to give back and of course, we will NEVER let go of the "It'll be done two weeks" jab.:music_whistling:

Thank you!

I understand. I picked up on Skulleaders JSGME path right away and knew it would not work correctly with my setup so modified the file structure accordingly just like you did). The mod installs fine in all three iterations so I have the structure right. But I am puzzled as to why, regardless of how many efforts I make, I cannot get the brown "No Hand Hold" pad in the final release P-51D. I get it in the Beta release and the Alpha (with his 1.8 version) and every other aspect of his mod is there, the armrest, the colored gages, the footprints, everything as you can see in the "screens" I posted, except that darn pad color. I even open the ZIP file and look at the .dds files and the associated .bmps that Skulleader uses, and they clearly show the brown pad except when I enter the cockpit of the Final release, it is black. Needless to say, I'm stumped. Thanks for your help and advice.

Yes. Skulleader, Although that specific path does not work on my computer since I have my DCS World folders on a separate SSD from the OS. But I am very familiar with the JSGMS file protocols so I have it installed accordingly. As I stated earlier, the same JSGME that works for the Beta install works for most all of your mod when installed into the stable version, except for that "No Hand Hold" pad color. I have even tried copying and pasting your .bmp file from your last release that contains the brown pad, but it STILL shows as black in the Release version. It is brown in both my Alpha (using your 1.8 version) and Beta (using the most recent version) installs. I won't take any more of your time as this is not that big an issue. It is just that it frustrates me when something does not work as usual and I cannot figure out the reason. I'll live with it. Again, thanks for your attention to this and your help. JJohnson241, I have changed the JSGME file path just like you indicated, and with several other file protocols as well while trying to figure this out. It appears that is NOT the issue. I have JSGME for all three installs Final Release, Beta, and Alpha. The file path I use works just fine with all three with the exception of the darn "No Hand Hold" pad being black in the final release. I even installed the Zip file contents of Skulleaders mod directly into the mods, aircraft, P-51D, Cockpit, Textures Zip directly and over rode the regular Zip files. The issue is still there. I think it will remain a mystery until I somehow stupidly stumble over the cause. If I understand correctly, the current Final Release and the Beta release are pretty much the same where the P-51D is concerned as it is out of "beta", so ANY JSGME should work equally for both those installs, right? Given that the Final Release and the Beta are NOT using the EDGE graphics, I don't seem to have any issues with any JSGME mod in any of the installs EXCEPT this one. I have even done a repair to make sure the installs are in right, and still the issue persists.

Have you by any chance... ..had an opportunity to examine the shudder that is taking place once the landing gear doors of the Mustang have fully deployed on shutdown? Not a deal breaker but I recall you saying you would look into it. Thanks.

Skulleader, Thanks for trying. I have downloaded and installed your latest mod. To let you know how weird this is, I placed your latest mod into my Beta install and it also has the black "No Hand Hold" pad. I removed it and put your version 1.7 back into the Beta and voila', back to the brown pad. I then put version 1.7 into my install of the Final Release and it's back to the black pad. I simply am in over my head on this so will accept that I cannot fix the issue and learn to live with the black pad. It's really not a deal breaker as every other part of your mod is there, just not the brown pad. It is really baffling in light of the fact that we both have the same install and you have the brown pad. I even removed all my JSGME mods, did a "repair" and reinstalled those mods. Same issue. I give up! Again, thanks for a truly great "pit" for the Mustang and also trying to help me get to the bottom of this.

Still an issue. Skulleader, I am not able to download that link on DropBox but I do have your latest release dated 7-23-29016 but still I have the problem. Here are some screenshots showing what is happening. This one is from the same mission only in the Final Release: This second one is from the Open Beta: The same release of your mod is installed in both .

Skull, Perhaps you can help with an issue I am having with your cockpit. I have the same mod 1.8 installed in both the Final Release and the beta release. Both have the latest 1.54 updates as of today. When I fly the Mustang in the Final release, the padded "No Hand Hold" portion is black, not the brown as in your mod. It is brown in the Beta release as always. I have tried copying and pasting the whole P-51 "Cockpit" folder from the Beta to the Final release but no matter what I do, that pad still comes up black, not brown. The rest of the cockpit is all correct for your mod. Any ideas?

Okay. I must have got ahead of the curve somehow. I just updated the Release version to the latest release. Went back and ran an update on the Beta Release and it updated to the latest release as well. Thanks ED!!

Open Beta I was wondering the same thing, but only the Beta updated. I did notice after the update that my version from 1.54.54855 remained the same. It did not update the version to the newer DCS 1.5.4.55169 that was indicated in the release. Don't know if that matters or not, but did pick up on it.