Revision 121

 

• - don't load gdipp on XP (fixes SRWLock error)
  - don't load vertex/index buffer on dedis
  - fix loading of fastfiles when cdpaths are used
   
  external changes related to this update:
  - add vision files to updater
  - remove key dependency from FifthInfinity
  - possible fix for a crash during loading of nuked

 

Changes:

 

• (modified) clientdll/steam_api/PatchMW2SPMaps.cpp
  
• (modified) clientdll/steam_api/PatchMW2Load.cpp
  
• (modified) clientdll/steam_api/PatchMW2.cpp
  
• (modified) clientdll/steam_api/PatchMW2CModels.cpp

 

Committed by ntauthority on 2013-02-08 - 10:12:37

What does 'removing key dependency' actually do ?

{ "mp_rust", "weap_trey" },

{ "mp_cross_fire", "iw4_wc_shaders" },

{ "mp_rust", "weap_trey" },

{ "mp_cross_fire", "iw4_wc_shaders" },

Nice to know that new fastfile builder works so well.

1000 w00t

We want "extdll"

We want "extdll"

not getting it

I just want the new weapons and persistence changes

We want "extdll"

not getting it

So there is no need to maintain the svn anymore!

We want "extdll"

+1

We want "extdll"

+1

But it won't be released. (open-source I believe)

We want "extdll"

+1

But it won't be released. (open-source I believe)

Still a legit wish. I loved that this project was open-source, why cannot you just ignore those stealing idiots?

I mean we all now, that it is NTA's work, and most important, he knows, that this would not be possible for any(!) platform without him, so whats the deal of keeping mp_nuked 4D1-only at the expense of legit modders ..

Still a legit wish. I loved that this project was open-source, why cannot you just ignore those stealing idiots?

LetВґs say you will create soemthing. Now I will steal it and donВґt give credits. Are you happy about it? I think not

Revision 121??? I still have 120... Why that? I already deleted caches.xml and updated...

ItВґs not pushed through the updater

Still a legit wish. I loved that this project was open-source, why cannot you just ignore those stealing idiots?

LetВґs say you will create soemthing. Now I will steal it and donВґt give credits. Are you happy about it? I think not

Let's say I did actually created something. And this little something has already 150k users, so I guess, I can at least try to imaging what that would mean to me, if you would steal it. That said, I can at least roughly estimate, what I demand. So, yeah, sure I would not be happy about it, but I would not try to defend you stealing my code, by limiting my work for all users. That may sound very drastic, because we all are still able to play the game, enjoy the new content and mod the shit out of it, but the project is definitely losing some quality at this point for me.

To me this even means that the AlterRev guys did won in some aspects. They got enough users to get NTA to go closed-source with this project. I guess this is their first self-made achievement, I hope they are proud.

ItВґs not pushed through the updater

It is, just labeled wrong.

Also I believe that NTA only published the source to compile with Q3-licenses (derivate work should be published).

As the extdll isn't an "essential" part of iw4m that license isn't violated (note that I'm no lawyer) and his work is "protected" from unauthorized use.

Sure it would be better to have the source but if the author doesn't want to publish it we'll have to accept that imo.

the primary problem with full open-source code releases and the ensuing forks-without-improvement is that it causes a) community separation, lack of control over the main public branch (especially important due to client/server compatibility), c) various support issues because people all assume it's 'the same game' , and some more stuff I likely forgot to mention.

 

Anyway, certain components may be released as open-source in the future, the SVN will continue to be maintained, and custom client DLLs are still possible if you sign the code with a certificate valid according to the local Windows certificate store.

[...] and custom client DLLs are still possible if you sign the code with a certificate valid according to the local Windows certificate store.

That is a good idea

[...] and custom client DLLs are still possible if you sign the code with a certificate valid according to the local Windows certificate store.

That is a good idea

it would be great

how to load the nucked map i try /devmap nucked

/devmap mp_nuked

how to load the nucked map i try /devmap nucked

/devmap mp_nuked

how to load the nucked map i try /devmap nucked

/devmap mp_nuked

And that's a perfect example of you postwhoring

how to load the nucked map i try /devmap nucked

/devmap mp_nuked

And that's a perfect example of you postwhoring

And your post isn't ? Admit it, I helped the guy out ;p

how to load the nucked map i try /devmap nucked

/devmap mp_nuked

And that's a perfect example of you postwhoring

And your post isn't ? Admit it, I helped the guy out ;p

I think he meant because of the post above yours.