terminator363 Posted October 1, 2015 Share Posted October 1, 2015 Happy Bug Hunting! Link to comment Share on other sites More sharing options...
Wizard_03 Posted October 1, 2015 Share Posted October 1, 2015 Me too no Tac numbers on any skins DCS F/A-18C :sorcerer: Link to comment Share on other sites More sharing options...
Cobra847 Posted October 1, 2015 Share Posted October 1, 2015 Seems to be machine dependent. (Works fine on some, not so much on others) Will investigate. Nicholas Dackard Founder & Lead Artist Heatblur Simulations https://www.facebook.com/heatblur/ Link to comment Share on other sites More sharing options...
Art-J Posted October 2, 2015 Share Posted October 2, 2015 For example, on my machine, the Russian camo skin works fine, bort numbers and all, but the "2.0 test" one is glitched like on the OP's screen above. Haven't tested the others yet. 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...
-Rudel- Posted October 2, 2015 Share Posted October 2, 2015 As I've mentioned before, the 21 uses a unconventional use of tac numbers not supported 100% by ED's code. I'll write up a how-to after I finish testing with the 3d model. https://magnitude-3.com/ https://www.facebook.com/magnitude3llc https://www.youtube.com/@magnitude_3 i9 13900K, 128GB RAM, RTX 4090, Win10Pro, 2 x 2TB SSD i9 10980XE, 128GB RAM, RTX 3090Ti, Win10 Pro, 2 x 256GB SSD, 4 x 512GB SSD RAID 0, 6 x 4TB HDD RAID 6, 9361-8i RAID Controller i7 4960X, 64GB RAM, GTX Titan X Black, Win10 Pro, 512GB PCIe SSD, 2 x 256GB SSD Link to comment Share on other sites More sharing options...
terminator363 Posted October 2, 2015 Author Share Posted October 2, 2015 As I've mentioned before, the 21 uses a unconventional use of tac numbers not supported 100% by ED's code. I'll write up a how-to after I finish testing with the 3d model. Thanks for looking into this Happy Bug Hunting! Link to comment Share on other sites More sharing options...
Wizard_03 Posted October 2, 2015 Share Posted October 2, 2015 Thank you, new skins are awesome btw DCS F/A-18C :sorcerer: Link to comment Share on other sites More sharing options...
terminator363 Posted October 2, 2015 Author Share Posted October 2, 2015 I read somewhere that we would be getting like 20 new skins? What happened? I only have like 5 or 6. Happy Bug Hunting! Link to comment Share on other sites More sharing options...
BlackLion213 Posted October 2, 2015 Share Posted October 2, 2015 (edited) As I've mentioned before, the 21 uses a unconventional use of tac numbers not supported 100% by ED's code. I'll write up a how-to after I finish testing with the 3d model. Great, thank you! I am one of the unlucky, but the upgrades to the model and skin are really impressive! My long-time favorite skin is the VVS Grey and the upgrades really bring it to life. Frankly, it looks awesome even with holes in the fuselage. :thumbup: Also, the flight model upgrades are excellent, much smoother escalation of AOA as you slow below corner speed, seems more realistic. Overall, I'm VERY happy with the improvements, even more so once these few small glitches get worked out. Thank you for continuing to upgrade the best module in DCS. :D -Nick PS - LOVE the Beta 2.0 skin. I think MiGs look great in natural metal - that classic "evil empire" look from my youth. :D EDIT: Interesting finding with the missing textures - it doesn't effect instant action missions. If I pick the camouflaged Russian skin (185th) on "Create mission" the glitch is present. The same skin on "Instant action" is working perfectly. Hope this helps to track it down. Edited October 2, 2015 by BlackLion213 Link to comment Share on other sites More sharing options...
Esac_mirmidon Posted October 2, 2015 Share Posted October 2, 2015 This texture problem shows only when you change the default bort number. If you put a new Mig-21 in the mission editor and don´t touch the bort number, everything runs fine. Only if you change the bort number. " You must think in russian.." [sIGPIC][/sIGPIC] Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´ Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4 Link to comment Share on other sites More sharing options...
Art-J Posted October 2, 2015 Share Posted October 2, 2015 ^ I don't think this is a definitive answer, as I noticed the glitch in random quick mission without changing anything except the skin (to the 2.0 test version). Further testing is going to be necessary. 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...
terminator363 Posted October 2, 2015 Author Share Posted October 2, 2015 I never changed these settings and I still have the missing texture :/ Happy Bug Hunting! Link to comment Share on other sites More sharing options...
rrohde Posted October 2, 2015 Share Posted October 2, 2015 This texture problem shows only when you change the default bort number. If you put a new Mig-21 in the mission editor and don´t touch the bort number, everything runs fine. Only if you change the bort number. Negative on that statement. Haven't messed with the editor, nothing, and got the same issue off the bat: PC: AMD Ryzen 9 5950X | MSI Suprim GeForce 3090 TI | ASUS Prime X570-P | 128GB DDR4 3600 RAM | 2TB Samsung 870 EVO SSD | Win10 Pro 64bit Gear: HP Reverb G2 | JetPad FSE | VKB Gunfighter Pro Mk.III w/ MCG Ultimate VKBcontrollers.com Link to comment Share on other sites More sharing options...
Wizard_03 Posted October 2, 2015 Share Posted October 2, 2015 ^agreed I used create fast mission and just changed the skin and load outs when I discovered this. Did not mess with the bort numbers DCS F/A-18C :sorcerer: Link to comment Share on other sites More sharing options...
BlackLion213 Posted October 2, 2015 Share Posted October 2, 2015 (edited) ^agreed I used create fast mission and just changed the skin and load outs when I discovered this. Did not mess with the bort numbers Interesting, I also use "Create Fast Mission" and only change the skin - no Bort changes - but mine is missing textures. However, my "Instant Action" missions are fine. Maybe create fast mission is attempting to change the Bort numbers for some reason on certain machines? When I get home from work tonight, I'll create a test mission in the mission editor and see if that has the same issue. -Nick PS - I hope these issues can be sorted with your current Bort number system. The rendering and appearance of these numbers is MUCH nicer than the standard Borts, which to me are often a weak point visually. Edited October 2, 2015 by BlackLion213 Link to comment Share on other sites More sharing options...
Art-J Posted October 2, 2015 Share Posted October 2, 2015 Yep, the skins on stock instant action missions seem to display correctly. But in any fast missions created by the user, the same skins get glitched as shown above. That's a bit strange. 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...
Wizard_03 Posted October 2, 2015 Share Posted October 2, 2015 Interesting, I also use "Create Fast Mission" and only change the skin - no Bort changes - but mine is missing textures. However, my "Instant Action" missions are fine. Maybe create fast mission is attempting to change the Bort numbers for some reason on certain machines? I think you right. Has anyone tried the LN single missions or training missions? DCS F/A-18C :sorcerer: Link to comment Share on other sites More sharing options...
bart Posted October 2, 2015 Share Posted October 2, 2015 I have this issue also......see sig for PC specs. I thought it might be a corrupt download so un-installed the beta, then did a full fresh install. Same result. I even had to use an activation to get it working in the beta...strange as its on the same drive as my main installation. Down to 1 life left now :( I also cant get the throttle to work either on my hotas, it shows up red on thecontrol bindings. Left throttle works fine on brakes lever on the stick. Has anyone else had this? System :- i7-12700K 3.6 GHz 12 core, ASUS ROG Strix Z690-A Gaming, 64GB Corsair Vengeance RGB Pro 3200MHz, 24GB Asus ROG Strix Geforce RTX 3090, 1x 500GB Samsung 980 PRO M.2, 1x 2TB Samsung 980 PRO M.2, Corsair 1000W RMx Series Modular 80 Plus Gold PSU, Windows 10. VIRPIL VPC WarBRD Base with HOTAS Warthog Stick and Warthog Throttle, VIRPIL ACE Interceptor Pedals, VIRPIL VPC Rotor TCS Plus Base with a Hawk-60 Grip, HP Reverb G2. Link to comment Share on other sites More sharing options...
unknown Posted October 2, 2015 Share Posted October 2, 2015 I placed a mig-21 in the mission editor and have no problems with the skin! Tryed every skin in the list and all worked like they should. Than i changed the tail number from 010 to 13 and i got the same problem as you mentioned. I changed the tail number than to 013 and everything was working again. It seems you need a leeding 0 befor the number? Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
Wizard_03 Posted October 2, 2015 Share Posted October 2, 2015 Interesting yeah I just had a value of 9 in the tail number box when I was experimenting. I will try that asap DCS F/A-18C :sorcerer: Link to comment Share on other sites More sharing options...
terminator363 Posted October 2, 2015 Author Share Posted October 2, 2015 Honestly it shouldn't matter what game play mode you use. This glitch shouldn't exist. Happy Bug Hunting! Link to comment Share on other sites More sharing options...
unknown Posted October 2, 2015 Share Posted October 2, 2015 (edited) Interesting yeah I just had a value of 9 in the tail number box when I was experimenting. I will try that asap It seems the tail number has to be a 3 digit number. Trying 09 - > error, trying 009 everthing works just fine. And a leeding 0 doesn't be necessary, it works with 109 for example too. So, just make sure you have a 3 digit tail number and everything is fine. Edited October 2, 2015 by unknown typo Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
Wizard_03 Posted October 2, 2015 Share Posted October 2, 2015 It seems the tail number has to be a 3 digit number. Trying 09 - > error, trying 009 everthing works just fine. And a leeding 0 doesn't be necessary, it works with 109 for example too. So, just make sure you have a 3 digit tail number and everything is fine. It makes sense, since the numbers are not the exact same code that ED uses per Rudel's posts DCS F/A-18C :sorcerer: Link to comment Share on other sites More sharing options...
unknown Posted October 2, 2015 Share Posted October 2, 2015 Honestly it shouldn't matter what game play mode you use. This glitch shouldn't exist. I don't think it depends on the game play mode. I think it's the tailnumber not being a 3 digit number for that mission. Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
-Rudel- Posted October 2, 2015 Share Posted October 2, 2015 Please see this sticky thread: http://forums.eagle.ru/showthread.php?t=148308 https://magnitude-3.com/ https://www.facebook.com/magnitude3llc https://www.youtube.com/@magnitude_3 i9 13900K, 128GB RAM, RTX 4090, Win10Pro, 2 x 2TB SSD i9 10980XE, 128GB RAM, RTX 3090Ti, Win10 Pro, 2 x 256GB SSD, 4 x 512GB SSD RAID 0, 6 x 4TB HDD RAID 6, 9361-8i RAID Controller i7 4960X, 64GB RAM, GTX Titan X Black, Win10 Pro, 512GB PCIe SSD, 2 x 256GB SSD Link to comment Share on other sites More sharing options...
Recommended Posts