Doom3world

Just checked the materials and they're there (materials/sfx.mtr). Are you overriding the material file with your own?

Opps, yea I have a modified sfx.mtr, but those particles were never there in vanilla Doom. Did you move them from vp_materials to sfx?

Yes. I went through all files (materials, defs, etc.) and cleaned/organized everything. This is why there are so many "blank" files as their contents were either moved to a more proper file or removed entirely if they couldn't be used in any way.

Cool, I'll just merge my sfx file with yours to fix it. btw, I'm so glad I can finally play your mod now with catalyst AI turned off. It's very beautiful.

@RangerMcFriendly - Great video, but obviously you have a bug into .def, .mtr, .fx or .prt files, just track it for remove the black boxes you see for remove this easy bug, oh and maybe you just have the .tga but not the .dds version of that textures, try it !

@Sikkpin - When ? The ROE version for SikkMod v1.2 ???

Probably never.

Now that the source code is released many of the effect in Sikkmod could be replaced with ones more tightly integrated into the renderer.

The big downer is that since they didn't release the default ARB shaders as GPL folks can't take shortcuts and copy Sikkpin's methods or code. They'll either need to completely redesign the default ARB path (which would likely necessitate even more radical design changes for either the Sikkmod examples or other shader mods) or use Raynorpat's GLSL path (and write GLSL shaders from scratch).

OTOH, mods have already been distributing the entire glprogs code for years without GPL blessing. What would be the difference if it were included with a compiled source executable? You could just write a disclaimer that you must own Doom 3 to use the glprogs? Of course, commercial standalone games wouldn't have this option.

What do you mean? All of my shaders are 100% custom so you don't need id's shaders to have be GLP'd in order to use my shaders in a stand alone project.

*follows discussion with interest

Ok, don't care, because is so easy for me to take the changes in v1.2 and update the previous v1.1 ROE version, but because before you made the both versions and i see other people asking for the ROE version, is clean there is interest for that version of this good mod, but if you not care for them, its okay.

Oh, for fuck's sake...

Perhaps you should apologise to the man.

@nbohr :

Where does the notion come from that people cannot just make their own customized ARB VFP Files for Source Projects ?

Afaik id not releasing their VFP files does not mean that the ARB Path is somehow out of the question, just because some VFP files ( like the one for shadow-volumes ) will wind up being similar, even when written "from scratch".

Most other default Doom3 VFP files leave loads of opportunity to optimize and change and improve anyway, even if they still use similar approaches to the original files. And people can build loads of custom additional ones of course.

Edit :

You guys have probably noticed by now that dafama is struggling with english a little and may not mean things in exactly the way they may sound ?

I'm sure dafama meant no harm.

Ah, but (without checking), you probably didn't explicitly state the licence for your media, so even if you did create it all from scratch, people don't actually have any right to use it with the gpl d3, without you first re-licensing it. Maybe you do explicitly state the licence, and I should probably check first, but it's a reasonable assumption since all your c++ code is not GPL compatible as it is bound by the original sdk EULA where you got it from, unless you have reissued it with the GPL statements etc.

Hmm...

There was a big blowup about the missing ARB shaders in the GPL release over at Github. Many over there were implying that
any derivative work would not be kosher to distribute.

I have no doubt that Sikkmod is radically revised from the shaders that ship with Doom 3 but is there no component
that is derived from the original code?

That was the presumption. Even a minor reference that could be construed as derivative of the original ARB code would
be in jeopardy of violating Id Software's property rights.

But yeah, I guess that's the far far far deep spectrum of paranoia from the hardcore GPL crowd.

If they really know a lot about open-source work maybe they do have a point, but it seems really strange to ship an engine source, and then stump the default rendering path due to some really simple pieces of code not being included.

Sure a different rendering-path like GLSL would make such doubts unnecessary, but i find it really hard to believe that id will sue anybody because they happen to be reading from the same texture-units ( that the engine binds to in the first place, unless you juggle that around a bit, just so your VFPs look a bit less similar ), or normalizing a vector with a similar series of instructions in a custom VFP file. Some basic inner workings would have to be the same or done similarly tho, if you use the ARB2 path for example.

( Btw this is not supposed to be a case for any specific shader mod, there have been many custom VFPs by many authors over the years, just the general question if the ARB path is generally a no-go for stand-alone projects )

I really don't think that's how it works since the shaders are not id/Doom 3 specific and are full of just generic math which can not be "owned". By that rationale, writing a line that simply samples the diffuse map can't be used as it will end up being written exactly the same as how it's written in id's non-gpl shaders. That doesn't make sense to me.


@AnthonyJa
I don't need to declare a license in order for my work to be used in a GPL project, this goes for shaders and C++ code.