Madmatt_BFC

There are a few different mods out that aim to address this issue and while some of them work well in daylight missions, pretty much none of them work during night or low light missions. The full fix for this will seem to have to wait for the ED updated cockpit. Madmatt

Yes, it works pretty well... during daylight. I think you may find that at night or low light conditions it suffers the same issues. I seem to recall that this was because the current shaders are not illuminating the lights properly from within the buttons but rather reflecting the ambient lighting in the scene. If there is no or low background light to reflect, the buttons loose their perceived illumination. I've tried all the mods that supposedly resolve this issue but none of them work 100% in all lighting conditions. Hopefully, the ED updated Ka-50 cockpit is not too far away. Madmatt

Order #1276 just placed. Can't believe I missed this thread for so many months. The timing couldn't be better though as I just started getting back into flying the A-10C in VR and was really struggling with that terrible stock slew control. Can't wait to get this installed and report back my results! Madmatt

With this mod it's definitely better and you can more easily tell when the AP buttons are pushed now but I would still like to see Deferred Shading properly fixed by the devs. Just have to be patient as they are aware of the issue. Madmatt

The light mod and the updated cockpit mod posted by Devrim work very well together when using Deferred Shading while we wait for an official fix from ED. Madmatt

Looks like I too spoke too soon. I started playing in VR again and now I am getting the crashes on exit again as I did before. Log file attached. Madmatt dcs.log-20180216-033442.zip

Pretty sure he means just running the normal Oculus Sensor Setup again. Madmatt

I had this problem too until I added more sensors. I am now running 4 sensors (each one basically in a corner of my gaming room) for full roomscale and I run all the sensors on a dedicated 4 port powered USB card. That made a huge difference for me. Do you only have one sensor available? Have you tried rerunning the sensor setup to see if that improves things at all? Check in the Devices Tab inside of the Oculus Home program and see if Oculus is seeing that sensor as a USB 3 device, same with your headset. Just a few ideas, but yes i did have the exact same issue as you from time to time and it seemed to be related to poor sensor tracking. Now you have to try and isolate WHY you have intermittent poor tracking. Oh, one last thing, make sure and disable any and all power savings features on your USB devices inside of Windows device manager. That can also cause havoc with the Oculus. Madmatt

I have not gotten a crash on exit since the hotfix. So for me at least, it seems to be resolved and I have launched and exited the game about 20 times already. Madmatt

Now that I have had more time with the various profiles I see what you mean. I am already learning to adapt to the S3 usage and continue to be impressed by the elegance of your scripts. Thank you for the reply! Madmatt

Home Fries, First off let me express my huge amount of respect and admiration for all the work that has gone into your utility. The documentation alone is truly exceptional. I've had my Warthog since last year and only recently started doing my own programming but what you have accomplished is amazing. Now, I have mostly been using it with the KA-50 which I have been flying much more with the release of 2.5 and I have run into a slight issue. Using the S3 key as the "shift" key is a bit cumbersome and in all my homemade profiles I have instead used the S4 paddle as my primary modifier. Would it be possible to give us the ability to switch the shift key from S3 to S4 for the Ka-50 profile? Perhaps make that an option in the Settings panel? If not, how hard would this be to hand edit myself? Could it be as easy as searching the existing script and replacing all instances of "S3" with S4 and vice versa? Another issue I have noticed is purely cosmetic but for some functions the button position on the throttle doesn't seem to mimic what it is on screen or in your overlay guide. What I mean is that some buttons seem upside down from what they show on screen. Click the switch down shows the opposite function (switching up) in game. I have noticed this on a couple of switches. I have tried this with both the in game "Sync controls to HOTAS at startup" setting enabled and disabled and it didn't seem to matter. I first noticed this with the burst selector switch. Pushing the switch down doesn't make it flip down in game. All three settings are possible but the switch in the game doesn't match the position on the controller (ex: to get the middle position I have to push the switch down, leaving it in the middle shows the top position in game and clicking it up moves the switch to bottom setting). Im going from memory here so I may have gotten the order wrong. I will check ingame and list exactly what I am seeing. A minor issue and may be on purpose because of how those switches work but just something I noticed. I'm away from my HOTAS this morning but when I get home I can send you the details on which switches I have noticed seem out of sync. Again, none of this is meant as a complaint. What you have done with TARGET is stunning and I am a huge admirer of your work. So much so that I just placed an order for a set of the Thrustmaster MFD's even though I primarily play in VR. Thanks again for your time! Madmatt

I recently replaced my trusty Logitech G510 with a Corsair K70 LUX RGB keyboard. The feel of the mechanical keys is amazing. It's simply a joy to type on. I liked it so much that I also bought a Corsair Strafe keyboard for my second gaming rig with the new Silent Cherry switches. Typing again feels amazing but its a little more quiet with less "klackity klack" of the keypresses. I've been really enjoying all the customizations possible with the LED features and have been experimenting with different color layouts depending on the planes I fly. They aren't cheap keyboards, but IMO worth every penny. The only thing I miss is the dedicated LCD panel on my old 510. I used to display various system details on that (CPU temp, GPU, temp, GPU speed, Framerate etc..) using ATI Afterburner but I just moved those settings to a toggleable in-game overlay which works almost as well. http://www.corsair.com/en-us/k70-lux-rgb-mechanical-gaming-keyboard-cherry-mx-red-na http://www.corsair.com/en-us/strafe-rgb-mechanical-gaming-keyboard-cherry-mx-silent Madmatt

Windows 10 Pro N, x64, all updates in place.

I have bought 3 different versions of Black Shark going back to the first BS1 Russian version in November of 2008 so it's safe to say this has long been a favorite module of mine, although over the last few years it been getting a bit dusty as I've picked up and learned newer aircraft. With the release of 2.5 into Open Beta, and the advances to the tree rendering specifically, the Ka-50 and the other helo modules were high on my list to get back into with fervor. I was sad to see this lighting issue in both the default and moded cockpits that I use and will remain hopeful that ED gives it some attention soon. It is still playable of course, the biggest issue for me is that its a bit tricky to determine which of the 4 autopilot channels is currently engaged although that can be felt easily enough while flying once you get the hang of it. In fact, last night I decided to do a little bit of 2.5 sight seeing around the Beslan airdrome. After I did a smooth hover check, i flew off and just admired the trees and terrain. It was heavily overcast and foggy with visibility limited to maybe 1 Km or so. I kept my airspeed at around 50-60 knots and altitude at tree top and lower. It was amazing! I was in VR which makes it even more thrilling but the old girl still looks pretty and handles like a sports car. I flew out for maybe 20 minutes or so, over trees and under power lines. In the past, there were times were often I fought with the autopilot but now with age, patience, hard won skill and a extended Warthog HOTAS (:)) everything just felt so right. I finally turned back around and did some dead reckoning navigation and picked up the airfield lights shining in the fog. For the first time in nearly 10 years of flying the Shark I did a proper and smooth landing without crunching my gear, being riddled with holes, or coming in too hot and much too fast. Nope, everything was nice and slow and precise and it was a dream to fly her. I can't wait to take her out again. Thank you ED for giving me experiences like that, and when priorities and time permit, I look forward to this current lighting issue being resolved so others can have this same level of enjoyment with this DCS module... The first one that I truly ever loved. Madmatt

I too have been having this same issue, although for me it's been occurring for several months in both 2.2 and 1.58. When 2.5 Open Beta was released I performed a full reinstall but the crashes still occur about 4 out of 5 times when i exit the game. I play in both VR and normal and both modes crash at same frequency when I exit to desktop. Most recent crash logs attached along with the associated Application error log from Windows. I have a second gaming rig that I sometimes play on which does not crash on exit at all. This is far from a gamebreaker issue, but it is annoying that my favorite game does not exit cleanly. Thanks! Madmatt Faulting application name: DCS.exe, version: 2.5.0.14044, time stamp: 0x5a797ffc Faulting module name: dx11backend.dll, version: 2.5.0.14044, time stamp: 0x5a778044 Exception code: 0xc0000005 Fault offset: 0x0000000000015e86 Faulting process id: 0x54 Faulting application start time: 0x01d3a0830feee000 Faulting application path: C:\Games\DCS World OpenBeta\bin\DCS.exe Faulting module path: C:\Games\DCS World OpenBeta\bin\dx11backend.dll Report Id: 7da7a34e-f275-4c97-9680-235a640c2388 Faulting package full name: Faulting package-relative application ID: dcs.log-20180208-032536.zip dcs.log.txt

Just a quick note that Milan is on vacation until August 16th so you may have to wait a bit for your answer. In other news, just got my new set of Crosswind rudders last week and as everyone else that already has a set has been saying... WOW! If anyone is on the fence, don't be. Order them now. They are truly THAT good. Madmatt

Serial (Stick and Throttle): #68597 Purchased July 10th, 2017 Location: Ohio Madmatt

Why am I deserving of this incredible offering? Because I have been playing flight sims for 30 years now and I have never used any gear other than CH Products stuff and would like to see what all the fuss is about with these new fangled Thrustmasters! Madmatt

Here! Please take my money!

Apparently, in the DCS World Beta, the training does not yet work for the SU-25T. Madmatt

Yup, I was facing the same issue myself. I cleared it up by just deleting the "Mods\aircrafts\Ka-50\bin" folder (which holds the exe and dll that allows the activation/deactivation of the module). That did the trick for me. I had no need to edit the registry but your mileage may vary. Madmatt

Hello, one week ago I opened up ticket # 13498 regarding needing a refresh of activations for my 7 year old copy of Flaming Cliffs 1. To date, I have not gotten any reply. Could I get someone to look at this ticket when possible please? Thank you! Madmatt p.s. I do realize that FC1 was superseded by FC2 (which I also own and is activated) but I would like to be able to get back into FC1.

Ah, here it is, enjoy! http://forums.eagle.ru/showthread.php?p=597201#post597201

Doesn't need to be a received DL target either since you can create your own target points with the ABRIS and Shkval. And those target points don't even need to actually be on top of real enemy units either since they are just virtual locations that the ABRIS keeps track of by their position based on their GPS coordinates under the Shkvals targeting gate. A while back I detailed exactly how this is done so you should be able to do a search on my name and find it. Apparently I was one of the first people (even some testers didn't know you could do it) to figure out this little trick. Yeah me! I also talked about how you could get wingmen to "patrol" between multiple waypoints by creating new Ingress and Target points using the Datalink and ABRIS. I will try and dig up that old thread as it had some great info in it that was not common knowledge at that time. Madmatt

Looks like I was mistaken slightly in my post above. I just had the problem again with the single player mode giving me that 000142 launch error again. This time, in order to get it to work, I did have to actually load a mission in Multiplayer mode first and then exit. I had thought that simply bringing up the MP UI would be enough, but apparently not. Oh well, at least I was able to get in to continue with my campaign. Oh, and thanks for the nice words slug88. Anyone that knows me, knows that I love good games no matter who makes them and have long tried to promote computer gaming and the smaller development houses whenever I can. Madmatt