Trooper117 Posted January 20 Posted January 20 Damn, been away for awhile, thought I'd check in to get some brand new skins for the remastered F-5... but no, the palaver still continues! 1
Rudel_chw Posted January 21 Posted January 21 1 hour ago, Trooper117 said: thought I'd check in to get some brand new skins for the remastered F-5... but no, the palaver still continues! Strange ... they show up fine on my updated DCS: For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
pyromaniac4002 Posted January 21 Posted January 21 39 minutes ago, Rudel_chw said: Strange ... they show up fine on my updated DCS: https://www.digitalcombatsimulator.com/en/files/filter/type-is-skin/unit-is-f-5e/apply/ Have you taken a look in here for any F-5 remaster skins?
Rudel_chw Posted January 21 Posted January 21 10 minutes ago, pyromaniac4002 said: Have you taken a look in here for any F-5 remaster skins? there are none yet, only skin for the old F-5 For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Netrunner Posted January 21 Posted January 21 I did notice there are now two Norwegian skins, one for 336 squadron and one for 338... but they are both exactly the same. 1 Intel 14700K, Nvidia 4080 Super, Kingston Fury 6000MHz 96GB RAM, NVME2 SSD, Thrustmaster Warthog HOTAS
sa63114200 Posted January 21 Posted January 21 (edited) As someone who has produced many skins in DCS, including five for the legacy F-5E, I would like to chime in and let ED know that without the ModelViewer support of this encrypted module, I will NOT be redoing/porting my skins for the Remastered F-5E. It is simply impractical that for every step in the production of a skin, we have to launch DCS, start a mission / the Mission Editor, pan around and zoom in for literraly hundreds and hundreds of times to finally achieve the end result we expect. Even with the ModelViewer available, producing certain skins can be timeconsuming, challenging and tedious (Chinook is a good recent example for me with all those many rivets that took forever to find - and some still remain unknown!) You remove the ModelViewer support, then the work becomes that much harder. In short, no ModelViewer support, no livery production for me! Edited January 21 by sa63114200 Improved text. 6
II.JG1_Vonrd Posted January 21 Posted January 21 2 hours ago, sa63114200 said: As someone who has produced many skins in DCS, including five for the legacy F-5E, I would like to chime in and let ED know that without the ModelViewer support of this encrypted module, I will NOT be redoing/porting my skins for the Remastered F-5E. It is simply impractical to launch DCS, start a mission / the Mission Editor, pan around and zoom in for literraly hundreds and hundreds of times to finally achieve the results we expect. Even with the ModelViewer available, producing certain skins can be extremely timeconsuming, very challenging and certainly tedious (Chinook is a good recent example for me with all those many many rivets that took forever to find - and some still remain unknown!) This! My fear is that all future modules will be like this, without access to the edm file in order to load the module into the Model Viewer. This would make QUALITY user user skins a thing of the past. @BIGNEWY @NineLine, is this the way of the future? 4
YoYo Posted January 21 Posted January 21 7 minutes ago, II.JG1_Vonrd said: This! My fear is that all future modules will be like this, without access to the edm file in order to load the module into the Model Viewer. This would make QUALITY user user skins a thing of the past. @BIGNEWY @NineLine, is this the way of the future? We need update Model Viewer for sure. +1 3 Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro
Trooper117 Posted January 21 Posted January 21 12 hours ago, Rudel_chw said: Strange ... they show up fine on my updated DCS: I should have said ''user made skins''... for the remastered F-5, sorry for that 1
MAXsenna Posted January 21 Posted January 21 I should have said ''user made skins''... for the remastered F-5, sorry for that Oh, well, then the answer is easy. None exists I guess, as the template was released yesterday, and the ones included are encrypted and those and the model can't be opened in Model Viewer IIRC. Sent from my SM-A536B using Tapatalk
Backy 51 Posted January 21 Posted January 21 ED has effectively terminated community skin creation for all of the new 3D model assets through encryption of shape and texture folder assets. Modelviewer 2 cannot open these EDCE files. Therefore, there is no way to derive the default Description.lua of a 3D shape file which is essential to creating skins. Additionally, without Modelviewer 2, you cannot easily view and test work in progress liveries without running DCS proper to view the unit being skinned. That is a completely untenable workflow process. The justification for this encryption action as posted on these forums is questionable. Is monetization of DLC livery "skinpacks" coming next? 6 I don't need no stinkin' GPS! (except for PGMs :D) [sIGPIC][/sIGPIC]
SkateZilla Posted January 21 Posted January 21 On 1/20/2025 at 12:06 PM, Megalax said: Agree to all the above, but to your number one point, could the model viewer be updated to have a drop down like the Mission Editor for models? So we may still access the model for viewing without loading the game? Model Viewer has many advantages and functionality that opening and closing the game multiple times to see a change in a livery is a big hassle. Perhaps ED can open a discussion with livery artists in order to see what it is that we would require to give out content? ModelViewer Currently does not have the DRM interface. 1 Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
denissoliveira Posted January 21 Posted January 21 Does anyone know how to use the skin, what is the name of the folder in liveiries for it to work? It's just for testing because I won't waste my time without modelview. I am a mod creator, and my work, besides being free, can even help sell more of the module, anyway, I believe that over time ED will release this feature. Through the community it makes a difference in the sale of the module. 1
MAXsenna Posted January 21 Posted January 21 ModelViewer Currently does not have the DRM interface. Ah, of course. Now I understand why they did it this way. Sent from my SM-A536B using Tapatalk
gulredrel Posted January 21 Posted January 21 Is the new SEA camo supposed to have the red stars on the exhaust pipe covers? Would better fit only for the Aggressor schemes / MiG-28.
Mach3DS Posted January 21 Posted January 21 A version of model viewer runs in DCS in the ME. The solution as I see it, for MV, is that we just need whatever version is running in the ME to be made into the stand alone. That way the 3D assets remain encrypted. But we can view our work. And create the Lua files etc as we've been doing for like a decade. The other thing we need access to are the default texture files. Without them you can't edit the Roughmets for example to create the quality skins. You want a change the flight suite or helmet? You need the default files. We can't be recreating every texture from scratch? You need to edit the RM for glossy paint vs matte camo or bare metal... for example. I don't think it's unreasonable to allow access to those. Ateast to paying customers. Who own the modules. 7 MACH 3 DESIGN STUDIO Heatblur Rivet Counting Squad™
Bucic Posted January 21 Posted January 21 @gulredrelUsing MSAA by any chance? F-5E simpit cockpit dimensions and flight controls Kill the Bloom - shader glow mod Poor audio Doppler effect in DCS [bug] Trees - huge performance hit especially up close
Doughguy Posted January 21 Posted January 21 (edited) i guess no more livery contests then, at least not in the way ED is currently dealing with things. Pity. Games stay alive due to mods. Edited January 21 by Doughguy 3 https://sr-f.de/
virgo47 Posted January 21 Posted January 21 3 hours ago, SkateZilla said: ModelViewer Currently does not have the DRM interface. And what is the future? I see people complaining about not knowing where it will go. Whether the modding will get harder, etc. Any stand on that? 1 L-39, F-4E, F-5E, F-14, F/A-18C, MiG-15, F-86F, AJS-37, C-101, FC2024 Yak-52, P-47, Spitfire, CE2 UH-1H, Mi-8, Ka-50 III, SA342 NTTR, PG, SY, Chnl, Norm2, Kola, DE Supercarrier, NS430, WWII, CA VKB STECS+Gladiator/Kosmosima+TPR DCS Unscripted YouTube "Favourite" bugs: 1) Object local camera fast/slow inverted, 2) Yak-52 toggles not toggling, 3) all Caucasus ATC bugs
Mach3DS Posted January 21 Posted January 21 4 hours ago, SkateZilla said: ModelViewer Currently does not have the DRM interface. I didn't see this until after I i posted...so, DRM loads with DCS which explains why ME version works? But we still need access to core texture files for custom stuff like helmets suits, Roughmets, if we want to edit the Normals for custom things like stiffener plates etc. I find it reasonable to encrypt if you don't own the modules, but not if your own them. So to me this issue is more than just a model viewer problem. 3 MACH 3 DESIGN STUDIO Heatblur Rivet Counting Squad™
waterman Posted January 21 Posted January 21 (edited) 10 hours ago, virgo47 said: And what is the future? I see people complaining about not knowing where it will go. Whether the modding will get harder, etc. Any stand on that? The future in DCS is probebly user pays for their exclusive addon skins. I learned my lesson and gave up with the Trains - not able to use them or create any with rotating wheels etc. User created mods dont make money and so are a pain for DCS. DCS do not help or like people who make mods. I would say all EDM files will be the new encrypted format in a couple of updates. Then all mods will be unusable and they have a locked up cash cow system . F35 is only a lot of words and funny when they cannot or wont fix simple requests like the train wheels and deactivation. Theres tanks being killed by small trees , rain crashing helicopters , planes vanishing in thin air , trains in the sky , and other ufo Ai planes crazy stuf White knuckle DCS test flights for the Real F35 Pilots im sure users can supply the .miz and .trk files for them to test So i think mods are being killed off to feed the greedy cash cow. Edited January 22 by waterman
sa63114200 Posted January 22 Posted January 22 1 hour ago, Mach3DS said: I didn't see this until after I i posted...so, DRM loads with DCS which explains why ME version works? But we still need access to core texture files for custom stuff like helmets suits, Roughmets, if we want to edit the Normals for custom things like stiffener plates etc. I find it reasonable to encrypt if you don't own the modules, but not if your own them. So to me this issue is more than just a model viewer problem. Well said. It's not just about the ModelViewer. It's also having access to the core texture files which thusfar we've had access to, and enabled us to do so much in terms of livery creation. I am wondering about ED's direction going forward. If we lose this access and capability, then DCS will lose a lot of its appeal and therefore success. 2 1
II.JG1_Vonrd Posted January 22 Posted January 22 I'm kinda surprised that we haven't heard word one (AFAIK) from ED about this subject. Livery makers have been commenting about since we noticed back in November that the S-3 was encrypted. I really hope that the comment by Waterman about pay skins is mistaken but I can't help but wonder. 1 1
Awacs_bandog Posted January 22 Posted January 22 2 minutes ago, II.JG1_Vonrd said: I'm kinda surprised that we haven't heard word one (AFAIK) from ED about this subject. Livery makers have been commenting about since we noticed back in November that the S-3 was encrypted. I really hope that the comment by Waterman about pay skins is mistaken but I can't help but wonder. Wags said on an interview with CW Lemoin it was a purposeful action to encrypt the new files because (and Im paraphrasing) "people were stealing our models" (paraphrased) 1 Livery Artist, Pilot, Not exclusively in that order.
II.JG1_Vonrd Posted January 22 Posted January 22 Just now, Awacs_bandog said: Wags said on an interview with CW Lemoin it was a purposeful action to encrypt the new files because (and Im paraphrasing) "people were stealing our models" (paraphrased) Ah Crap. What a shame. Perhaps the MV might be tweaked to read the encrypted files? Or a completely new MV? Even if possible it would be low priority. 3
Recommended Posts