Magic Zach Posted July 21, 2017 Share Posted July 21, 2017 K. This bug was from a month or so ago, and I never really thought of it as a bug until now. Screenshot: [ATTACH]166153[/ATTACH] I had gotten jumped by a 109 on my way back to Biniville at fuel economy mode. From behind me, he landed a little hit on me, but I saw no damage. ALSO, I had no engine problems. I had no decrease in power, OR any excessive shaking to the airframe after I got jumped. After I landed and shut down, I noticed that I couldn't see my blades. I ejected and walked around, and this is the sight I beheld. The bug part of this, is that I got no excessive shaking from the inbalance, or any decrease of power. I had flown for another TEN MINUTES after getting jumped by the 109, and I had no idea that for those 10 minutes, I had one blade! I remember it quite well, because it was quite the shocker when I found out. Hardware: T-50 Mongoose, VKB STECS, Saitek 3 Throttle Quadrant, Homemade 32-function Leo Bodnar Button Box, MFG Crosswind Pedals Oculus Rift S System Specs: MSI MPG X570 GAMING PLUS, RTX 3090, Ryzen 7 5800X3D, 32GB DDR4-3200, Samsung 860 EVO, Samsung 970 EVO 250GB Modules: AH-64D, Ka-50, Mi-8MTV2, F-16C, F-15E, F/A-18C, F-14B, F-5E, P-51D, Spitfire Mk LF Mk. IXc, Bf-109K-4, Fw-190A-8 Maps: Normandy, Nevada, Persian Gulf, Syria Link to comment Share on other sites More sharing options...
fiddlinjim Posted July 21, 2017 Share Posted July 21, 2017 Are you sure you didn't knock off the blades during the landing, happens to me all too frequently. Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted July 21, 2017 ED Team Share Posted July 21, 2017 without a track it is impossible to verify the circumstance of this, or reproduce for a report. I will keep a look out for it during my flights Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
Coxy_99 Posted July 21, 2017 Share Posted July 21, 2017 Just apply the brakes let it tip and yea that does happen :) Link to comment Share on other sites More sharing options...
Art-J Posted July 21, 2017 Share Posted July 21, 2017 OP says he landed and shut the engine down, in "normal" way I presume. So it wasn't a propstrike, cause If it was, he would've noticed the engine seizing immediately. I'd say there might be some discrepancy between visual vs. actual damage model in the Spit. After all, one doesn't quite have a proper resemblance to the other actually in either in DCS warbirds, so various silly things are observed on regular basis. The revised damage model cannot come soon enough! i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10. Link to comment Share on other sites More sharing options...
Magic Zach Posted July 21, 2017 Author Share Posted July 21, 2017 No, I did not strike the prop upon landing (though there was loss of paint on my wingtip). I did a three-point landing too. And, if one does have a prop strike in the Spitfire, I often notice that the Spitfire will be missing ONE blade, not THREE. I guess it's possible that the 109 just shot and hit my blades. They have a damage model while inflight. I accidentally rammed a 109 with my prop and lost a couple blades, as well as the engine seizing. I see no reason why that's impossible. What I find strange is that I had no loss of power or excessive shaking after I had gotten hit. Hardware: T-50 Mongoose, VKB STECS, Saitek 3 Throttle Quadrant, Homemade 32-function Leo Bodnar Button Box, MFG Crosswind Pedals Oculus Rift S System Specs: MSI MPG X570 GAMING PLUS, RTX 3090, Ryzen 7 5800X3D, 32GB DDR4-3200, Samsung 860 EVO, Samsung 970 EVO 250GB Modules: AH-64D, Ka-50, Mi-8MTV2, F-16C, F-15E, F/A-18C, F-14B, F-5E, P-51D, Spitfire Mk LF Mk. IXc, Bf-109K-4, Fw-190A-8 Maps: Normandy, Nevada, Persian Gulf, Syria Link to comment Share on other sites More sharing options...
Bounder Posted July 21, 2017 Share Posted July 21, 2017 (edited) I've seen a texture bug related to damage (once) - see attached images. In my case the bug occurred after I landed hits on this 109's wing. The missing texture popped back when I got closer. Edited July 21, 2017 by Bounder My PC specs: Win10 64 Pro, CPU i7-3820 4.4GHz, 16GB RAM, GPU Nvidia 1070 (8gb vram). Controls: Microsoft FFB2, Thrustmaster Warthog Throttle, MFG Crosswind Pedals, TrackIR5. My DCS Youtube Videos https://www.youtube.com/user/No64Bounder Link to comment Share on other sites More sharing options...
ED Team NineLine Posted July 21, 2017 ED Team Share Posted July 21, 2017 As BN said, we need a track for something like this to try and reproduce on our end in order to submit a bug. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
Bounder Posted July 21, 2017 Share Posted July 21, 2017 I know that Sith, but unfortunately that's the best I can do as I don't have the track file. All I can do is say what I say in my post and at least raise the possibility that the bug I describe exists. If I see it again I'll be sure to save the track. Cheers. My PC specs: Win10 64 Pro, CPU i7-3820 4.4GHz, 16GB RAM, GPU Nvidia 1070 (8gb vram). Controls: Microsoft FFB2, Thrustmaster Warthog Throttle, MFG Crosswind Pedals, TrackIR5. My DCS Youtube Videos https://www.youtube.com/user/No64Bounder Link to comment Share on other sites More sharing options...
ED Team NineLine Posted July 21, 2017 ED Team Share Posted July 21, 2017 Thanks, i'll keep an eye out as well. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
Magic Zach Posted July 22, 2017 Author Share Posted July 22, 2017 I've seen a texture bug related to damage (once) - see attached images. In my case the bug occurred after I landed hits on this 109's wing. The missing texture popped back when I got closer. +1 I've seen this bug as well Hardware: T-50 Mongoose, VKB STECS, Saitek 3 Throttle Quadrant, Homemade 32-function Leo Bodnar Button Box, MFG Crosswind Pedals Oculus Rift S System Specs: MSI MPG X570 GAMING PLUS, RTX 3090, Ryzen 7 5800X3D, 32GB DDR4-3200, Samsung 860 EVO, Samsung 970 EVO 250GB Modules: AH-64D, Ka-50, Mi-8MTV2, F-16C, F-15E, F/A-18C, F-14B, F-5E, P-51D, Spitfire Mk LF Mk. IXc, Bf-109K-4, Fw-190A-8 Maps: Normandy, Nevada, Persian Gulf, Syria Link to comment Share on other sites More sharing options...
ED Team NineLine Posted July 22, 2017 ED Team Share Posted July 22, 2017 Sounds like it's time for me to put some rounds in some parked aircraft with the Abrams again :) Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
ED Team NineLine Posted July 22, 2017 ED Team Share Posted July 22, 2017 I've seen a texture bug related to damage (once) - see attached images. In my case the bug occurred after I landed hits on this 109's wing. The missing texture popped back when I got closer. So tried to tear up some 109 wings and couldnt reproduce, I am using our internal RC so its possible its fixed, but either way, let me know if you see it again, I will continue to watch for it. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
Magic Zach Posted July 22, 2017 Author Share Posted July 22, 2017 I guess the Spitfire damaged prop bug shall remain a Spitfire superpower! :P Hardware: T-50 Mongoose, VKB STECS, Saitek 3 Throttle Quadrant, Homemade 32-function Leo Bodnar Button Box, MFG Crosswind Pedals Oculus Rift S System Specs: MSI MPG X570 GAMING PLUS, RTX 3090, Ryzen 7 5800X3D, 32GB DDR4-3200, Samsung 860 EVO, Samsung 970 EVO 250GB Modules: AH-64D, Ka-50, Mi-8MTV2, F-16C, F-15E, F/A-18C, F-14B, F-5E, P-51D, Spitfire Mk LF Mk. IXc, Bf-109K-4, Fw-190A-8 Maps: Normandy, Nevada, Persian Gulf, Syria Link to comment Share on other sites More sharing options...
Bounder Posted July 22, 2017 Share Posted July 22, 2017 (edited) So tried to tear up some 109 wings and couldnt reproduce, I am using our internal RC so its possible its fixed, but either way, let me know if you see it again, I will continue to watch for it. Thanks Sith. I had a little trouble remembering last night but I had to do a complete fresh install of DCS a week or two post the flight I captured those images (which is why I don't seem to have any tracks going back 4 weeks). I've not seen it since and so the bug may have been due/linked to a larger problem on my install. I guess the Spitfire damaged prop bug shall remain a Spitfire superpower! :P How do you know what you saw was actually related to the prop being shot off? You say you didn't experience any flight / engine problems and the only thing that suggests you had a problem was the view once you had landed. Is it not possible you may have seen a similar disappearing/see through texture bug on your prop like I saw on that 109's wing? Obviously until anyone sees anything like that again and uploads the track file it will remain a mystery. Edited July 22, 2017 by Bounder My PC specs: Win10 64 Pro, CPU i7-3820 4.4GHz, 16GB RAM, GPU Nvidia 1070 (8gb vram). Controls: Microsoft FFB2, Thrustmaster Warthog Throttle, MFG Crosswind Pedals, TrackIR5. My DCS Youtube Videos https://www.youtube.com/user/No64Bounder Link to comment Share on other sites More sharing options...
ED Team NineLine Posted July 22, 2017 ED Team Share Posted July 22, 2017 I guess the Spitfire damaged prop bug shall remain a Spitfire superpower! :P If you didnt notice I added [REPORTED] to the thread title, the Spitfie is Early Access, and there are a number of DM issues currently.. this to is one of them, and reported. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug** Link to comment Share on other sites More sharing options...
Recommended Posts