Jump to content

currenthill

ED Closed Beta Testers Team
  • Posts

    1978
  • Joined

  • Last visited

  • Days Won

    134

Everything posted by currenthill

  1. Thanks guys! I agree, let’s get back on track and on topic. Progress is good with the German pack and I will share some more pictures soon.
  2. Wow, you managed to disregard or misunderstand my post completely. Didn't I already say I completely understand the DCS T&C and EDs reasoning behind it, even if I don't agree with it myself? But you still seem to think the mesh is the mod. To humor you, I can tell you that the (common) license T&C I mentioned as an example in my post doesn't require me to mention the creator of the native editable mesh file. In the case I use a mesh with Creative Commons license type, I credit the author as by the license type in the README. Just like ED does when they use open source software. I even think I've credited you for some liveries. And what's up with the straw man about me naming a model? I've never said I create my meshes myself, it's even spelled out in my FAQ on my site. We should be more interested in how the modding possibilities of DCS are steadily declining. A couple of posts earlier I mentioned that even the weapon schemes are now encrypted. I just want to have the tools to make the best DCS mods possible. Well, it's been a pleasure, but I have to continue working on my assets now.
  3. Did you even read what I wrote? Not this again, we've had this conversation before. You seem astonishing immune to the information I give you every time you bring this up. You still seem to be under the impression that my mods are purchased 3D models which I release. I know you understand this better than this, so why play this game? But okay, I'll describe it for anyone else reading this. The models you purchase comes in an editable format (for example Blender, Max or FBX), they sometimes come with textures (which I rarely use), sometimes with UVs, but never with animations, code, sounds, collision models, destroyed models, documentation, testing etc which are needed for a well working asset. When I'm done with the mesh, adding the UVs, materials, textures, animations, connectors etc I export it to EDs proprietary EDM format. A format that doesn't allow editing without reverse engineering (which by EDs T&C is forbidden). For example, if you buy a 3D model from CGTrader, they will most likely come with what they call a Royalty free license. Here is how they describe the license T&C: "Royalty Free License allows you to use the product without the need to pay royalties or other license fees for multiple uses, per volume sold, or some time period of use or sales. You can use it as long as it is incorporated into the product and the 3rd party cannot retrieve it individually in either the digital or physical form. You cannot resell the model you bought in the digital or printed form, but can use it in your commercial projects multiple times after paying for it just once." "21A.2. The Buyer’s license to Product in this paragraph is strictly limited to Incorporated Product. Any use or republication, including sale or distribution of Product that is not Incorporated Product is strictly prohibited. For illustration, approved distribution or use of Product as Incorporated Product includes, but is not limited to: - as rendered still images or moving images; resold as part of a feature film, broadcast, or stock photography; - as purchased by a game’s creators as part of a game if the Product is contained inside a proprietary format and displays inside the game during play, but not for users to re-package as goods distributed or sold inside a virtual world;" "21A.3. If you use any Product in software products (such as video games, simulations, or VR-worlds) you must take all commercially reasonable measures to prevent the end user from gaining access to the Product. Methods of safeguarding the Product include but are not limited to: - using a proprietary disc format such as Xbox 360, Playstation 3, etc.; - using a proprietary Product format; - using a proprietary and/or password protected database or resource file that stores the Product data; - encrypting the Product data." You see, you need to separate Product from Incorporated Product. One can use the EDM without any issues, but one cannot redistribute or transfer the native editable model file. In the case of ED (as I mentioned in my earlier post), they have decided that they want to own the native editable model file, so that they can maintain it over time. If a third party would create models (like Massun or the Deka Chinese Pack) they could sell/transfer the native editable model file to ED because they own it. Let me reiterate - I know the EDs DCS T&C very well (Edit: It's actually TFC Ltd and not ED), and I know their requirements, that doesn't mean they're perfect. They can be changed in an instant if that's what they want. Believe me, I've written hundreds of contracts where IPR is a crucial part. That's why I commented on you calling it stupid talk. Does this make sense to you?
  4. It's not stupid talk. Outsourcing time consuming mesh work is a rather efficient way of reducing time to market as well as cost. You are correct in the fact that ED has taken upon themselves to create their meshes in-house, which naturally also applies to third parties or them integrating others work. It's their decision, but that doesn't mean it's a good decision. I understand that ED wants to have the native (editable) produced mesh with full rights to ensure the ability to maintain and develop it over time (think source code escrow). The other part he mentions, about providing tools for 'official modders' isn't stupid talk either. It's been proven rather successful in other platforms. I know that you're well versed in DCS modding and therefore you're also well aware of the fact that implementing DCS assets takes a lot more than a mesh, so please refrain from calling me a master at duplicating. That said, let's get back to what this thread is about. Status update As you might have guessed, there are new issues with the latest DCS update which have to be fixed. I'm getting very close to releasing the updated German asset pack. So I'll do my best to juggle the two at once.
  5. I did some tests of the MIM-104 assets and found that the LTAMDS (both stationary and HEMTT) has issues since the DCS update. The other radars, launchers etc works fine. I'll include a fix for the LTAMDS in the next US pack update. But until then, here are the updated files to fix the issue. MIM104_LTAMDS.lua MIM104_LTAMDS_HEMTT.lua
  6. Everytime a new DCS update is released I make a compare to see which files have been changed. This way I can find patterns of changes rather than test every single asset individually. One thing I noticed with this update is that ED seem to be locking stuff down even more, making it even harder for modders. A lot of the LUAs are encrypted since long time ago, and sincea couple of updates ago all the new ED assets are also encrypted (including the EDMs). With this update they seem to have removed access to the weapon schemes also. This means it's going to be much harder to create custom weapons. Modders are still relying a lot on old unencrypted 2.5x LUAs, and since ED are encrypting more and more parts of DCS, I'm running out of ideas of how to find information on how to implement new features.
  7. Yep, I've installed the new DCS update and I'm currently testing things...
  8. Sounds peculiar. In real life when most antiship missiles enters the final phase turns on its seeker and lock the target, then performs its final maneuver. A lot of missiles have pop-ups or a final speed boost. It all happens very quickly. In normal cases there shouldn't be possible for it to miss the target and then go around for another go. Especially since a lot of them have a downward trajectory, and it would be impossible to recover from either hitting the target or the water.
  9. Which ED missile are you thinking about?
  10. Thanks, I'll make a note of the issues.
  11. It refers to the original 1.1.0 version (I had to name the folder something). The incremental update works for every version from 1.1.0 and upwards. So just overwrite your USA pack folder with the content from the latest incremental file. Yep, it's hard to find a usable model of it.
  12. My main focus right now is systems that are in service or very close to be in service with the Germans. From that list only the IRIS-T SLM makes the list. But unfortunately I haven't found the TRML-4D radar yet.
  13. More German pack assets, the Skyshield with FCU and Revolver Gun Mk3 effectors.
  14. Yep, every DCS update is kind of bittersweet. I want the changes, but not the issues.
  15. Yep, it will be player controllable. Based on experience it's very likely a DCS update will break some or many of my assets.
  16. The only true ballistic missile in DCS is the core game Scud. I will continue my work of creating missiles with ballistic trajectories in DCS, but only time will tell if I'll be successful.
  17. Here's an overview of the current upcoming additions to the German asset pack.
  18. You're correct. When fixing the AARGM-ER I managed to disable its surface radar by mistake. The fix will be included in the next US pack update. Until then, here's the fixed file if you want to use both the AARGM-ER and the LRASM. B-21_Sensors.lua
×
×
  • Create New...