has anyone figured out merging prairie fire with vanilla content?

[Electric Messiah]

i got the new dlc a few weeks ago and i was gonna use EDEN with the MCC on it then try out modern weapons and future stuff on VC and civilians across the jungle but to my surprise those mod elements don't work with the dlc and i haven't been able to figure out enabling the new content on base arma 3 without directly modifying script or files. anyone know if there's a workshop item or a already proven method of implementing the content?

[SSG Anhor]

There is a reason for this ........ 1965 to 1975 none of these "modern" weapons and vehicles existed.
Why can't you stay within a story? The DLC explicitly deals with a historical era, and THAT is what makes this DLC so interesting.

[Broadsword]

Originally posted by SSG Anhor:

There is a reason for this ........ 1965 to 1975 none of these "modern" weapons and vehicles existed.
Why can't you stay within a story? The DLC explicitly deals with a historical era, and THAT is what makes this DLC so interesting.

????

Aside from not answering the OP's question, you've betrayed a rather interesting half-logic there: yes, you're correct that in a 1965-1975 era Vietnam, there wouldn't be any 'futuristic equipment,' but that in itself is only thinking one direction.

Why can't, pray-tell, the equipment of 1965-1975 survive into the future and correctly function alongside modern and futuristic equipment as they were intended by the designers? What, really, is the difference between an M14 from the SOG DLC and the Mk. 18 EBR from vanilla ArmA for the purposes of the player?

Why can't the elements of the DLC work with others? Shouldn't the DLC work correctly and in line with the other DLCs and ArmA's core content given that it's a paid mod?

I would hope that all these Creator DLCs come to some form standardization so that, yes, we can use them to supplement the platform that is ArmA. You can make a mission at any time, and any other mission maker can create a mission with just the DLC assets - or, you should be able to take and use any of the content across the multitude of mods, DLCs, and Creator DLCs available to make a mission if you choose, and that is what makes ArmA interesting.

[Karmaterrorᵁᴷ]

So if i buy the Vietnam DLC, i cant use the assets in vanilla arma?

Sorry this isnt an answer OP, i just assumed we could so its news to me. Defo dont want to buy it if i cant use assets and terrains from main game with the DLC and vice versa :(

[Chuck Jiggles]

Originally posted by Karmaterrorᵁᴷ:

So if i buy the Vietnam DLC, i cant use the assets in vanilla arma?

You can use the both CDLC assets together with vanilla ArmA 3 in 3DEN editor, so this is an incompatibility issue with MCC Sandbox and S.O.G, which means that the MCC needs to be updated to support it.

[29/P4TCH3R]

Originally posted by Broadsword:

Originally posted by SSG Anhor:

There is a reason for this ........ 1965 to 1975 none of these "modern" weapons and vehicles existed.
Why can't you stay within a story? The DLC explicitly deals with a historical era, and THAT is what makes this DLC so interesting.

????

Aside from not answering the OP's question, you've betrayed a rather interesting half-logic there: yes, you're correct that in a 1965-1975 era Vietnam, there wouldn't be any 'futuristic equipment,' but that in itself is only thinking one direction.

Why can't, pray-tell, the equipment of 1965-1975 survive into the future and correctly function alongside modern and futuristic equipment as they were intended by the designers? What, really, is the difference between an M14 from the SOG DLC and the Mk. 18 EBR from vanilla ArmA for the purposes of the player?

Why can't the elements of the DLC work with others? Shouldn't the DLC work correctly and in line with the other DLCs and ArmA's core content given that it's a paid mod?

I would hope that all these Creator DLCs come to some form standardization so that, yes, we can use them to supplement the platform that is ArmA. You can make a mission at any time, and any other mission maker can create a mission with just the DLC assets - or, you should be able to take and use any of the content across the multitude of mods, DLCs, and Creator DLCs available to make a mission if you choose, and that is what makes ArmA interesting.

The "only" standardization that you will see on those cDLCs is, that they are only optional loadeble content.
Anything else might not work, as both cDLCs are around 24gbs big.

[Broadsword]

Originally posted by 29j2003/The_P4TCH3R:

The "only" standardization that you will see on those cDLCs is, that they are only optional loadeble content.
Anything else might not work, as both cDLCs are around 24gbs big.

Do you have anything of value to add? Because size has absolutely nothing to do with compatibility.

Clearly DCS is incompatible with itself because every time a new map or plane is added, the size makes it incompatible.

Hell, have you never ran CUP and RHS together...? CUP and Unsung...? They're large mods and there is some performance problems from running two mods that size, but they're decently compatible.

The only thing incompatible as far as I can see isn't necessarily truly incompatibility, but different design practice: the majority of the Prairie Fire gear is significantly better because it's lighter - which isn't to say it doesn't work with other things. Clearly, this sort of lightening gear should be brought forward into the main game and the creator DLCs as well, since gear weight has been overstated massively.

[29/P4TCH3R]

Was an Awnser to that
"I would hope that all these Creator DLCs come to some form standardization so that"

Thats the only "standardization" that you will get.
But the people who created the cDLCs are open to make their cDLCs compatible with the others (referring to GM Devs). They do not need to do it as a requirement.
But as for now, they do work without a problem with normal Arma 3 and other cDLCs. Not like Contact.

[Broadsword]

I'm going to repeat my question: what part of size makes these DLCs incompatible?

I expressed an opinion and you used a very interesting dismissal. Please, I would like to know more about this.

[29/P4TCH3R]

I have never said that size makes these DLCs incompatible. Just said the only standardization that you will get, is that those cDLCs will only be optional DLCs because of their size.

[Broadsword]

Originally posted by 29j2003/The_P4TCH3R:

Anything else might not work, as both cDLCs are around 24gbs big.

See, the problem with telling someone on the internet you didn't say something, is that very often they can quote, exactly, what you said. Please keep this in mind in the future.

[29/P4TCH3R]

"The "only" standardization that you will see on those cDLCs is, that they are only optional loadeble content.
Anything else might not work, as both cDLCs are around 24gbs big."
Yes, not very good phrased I know, but the lower line is connected to the "standardization" part. Because it won't work if people need to download an extra of 48 Gigs for both cDLCs that they do not own.

[Broadsword]

Originally posted by 29j2003/The_P4TCH3R:

Because it won't work if people need to download an extra of 48 Gigs for both cDLCs that they do not own.

So you're saying that making sure these things play nice, simply won't work, because people don't own it...?

Perhaps you should see yourself out of the conversation as there are mods specifically designed for people who don't own these DLCs - that is, in large part, a major aim with the standardization.

https://steamcommunity.com/sharedfiles/filedetails/?id=1776428269&searchtext=global+mobilization+compatability

[29/P4TCH3R]

There where already a lot of complains even from 2016, where people stated, why do they need to download stuff that they dont own. (Refering to the Apex expansion)
That was one of the reasons why those cDLCs are only optional and not already pre installed like the other DLCs.
Size on the harddrives matters for a lot of people

[Broadsword]

So you admit there's nothing going wrong with compatibility, thank you and good day.

[29/P4TCH3R]

Yes. I didn't state otherwise.