| Shader Plugin / Shader Help [message #388741] |
Sun, 31 May 2009 13:32  |
 |
halo2pac
Messages: 659
Registered: December 2006
Location: Near Cleveland, Ohio
Karma: 0
|
Colonel |
|
|
I saw how Scrin and D6 did there huds, and it got me thinking on the possibilities of drawing things on Renegade's screen.
Since the only way to keep source private while still releasing it is with a plugin...
Is there a way to draw parts of the hud via a plugin?
Just like you would with "void __declspec(dllexport) UpdateHUD2()" from the Shaders.dll?
Rene-Buddy | Renegade X
Join the fight against Obsessive-Compulsive Posting Disorder. Cancel is ur friend.
*Renegade X Dev Team Member*
|
|
|
|
| Re: Shader Plugin / Shader Help [message #388751 is a reply to message #388741] |
Sun, 31 May 2009 14:26  |
 |
reborn
Messages: 3231
Registered: September 2004
Location: uk - london
Karma: 0
|
General (3 Stars) |
|
|
You couldn't keep the source private if you released a plug-in that was based on the scripts.dll shader's plug-in. It's still covered under the license agreement.
But yeah, you can draw thing on the screen with a shaders plug-in.
|
|
|
|
|
|
|
|
| Re: Shader Plugin / Shader Help [message #388768 is a reply to message #388755] |
Sun, 31 May 2009 19:15 |
|
halo2pac
Messages: 659
Registered: December 2006
Location: Near Cleveland, Ohio
Karma: 0
|
Colonel |
|
|
Ok that fixes that problem but why is it saying:
1>.\shaders.cpp(37) : fatal error C1189: #error :
The Renegade shaders.dll requires the DirectX August 2006 SDK installed in order to produce a proper executable.
If you wish to use a different version of the SDK, modify the delay load dll in linker settings to point to the newer d3dx.dll
I have
already set before it shows that error.
-
Attachment: l1.PNG
(Size: 9.50KB, Downloaded 477 times)
Rene-Buddy | Renegade X
Join the fight against Obsessive-Compulsive Posting Disorder. Cancel is ur friend.
*Renegade X Dev Team Member*
[Updated on: Sun, 31 May 2009 19:16] Report message to a moderator |
|
|
|
|
|
|
|
|
|
| Re: Shader Plugin / Shader Help [message #389865 is a reply to message #389859] |
Tue, 09 June 2009 15:50 |
 |
saberhawk
Messages: 1068
Registered: January 2006
Location: ::1
Karma: 0
|
General (1 Star) |
|
|
| Omar007 wrote on Tue, 09 June 2009 17:42 |
I know i have to do that but isnt the d3d9_30.dll already right?
It was added when installing the March 2009 SDK
So what do you thinnk would it be for March 2009 if this isnt the one?
PS. The only difference between his screenshot and mine if i where to post one is i don't have user32.lib in the Additional Dependencies. Although this is surely not the problem xD
|
March 2009 definately is not d3dx9_30.dll. I just don't feel like looking it up; the only confirmed DirectX SDK to build shaders.dll is the August 2006 one. Install that.
|
|
|
|
| Re: Shader Plugin / Shader Help [message #389903 is a reply to message #389865] |
Wed, 10 June 2009 03:04 |
 |
Omar007
Messages: 1711
Registered: December 2007
Location: Amsterdam
Karma: 0
|
General (1 Star) |
|
|
| Saberhawk wrote on Wed, 10 June 2009 00:50 |
| Omar007 wrote on Tue, 09 June 2009 17:42 |
I know i have to do that but isnt the d3d9_30.dll already right?
It was added when installing the March 2009 SDK
So what do you thinnk would it be for March 2009 if this isnt the one?
PS. The only difference between his screenshot and mine if i where to post one is i don't have user32.lib in the Additional Dependencies. Although this is surely not the problem xD
|
March 2009 definately is not d3dx9_30.dll. I just don't feel like looking it up; the only confirmed DirectX SDK to build shaders.dll is the August 2006 one. Install that.
|
Ah you where indeed right. It was the file from the August 2006 SDK :S
I only cant find the more recent one. ATM im guessing on d3dx9_41.dll
EDIT: nope its not working but supposed to be this one i believe :S
EDIT2: I found this in shaders.cpp:
#if D3DX_SDK_VERSION != 30
#error The Renegade shaders.dll requires the DirectX August 2006 SDK installed in order to produce a proper executable. If you wish to use a different version of the SDK, modify the delay load dll in linker settings to point to the newer d3dx.dll
#endif
AFAIK this means even if i do change the Delay Load to the newest (confirmed that is d3dx9_41.dll) it will still give this error. Seems it doesnt check if it is newer/older yes or no but only if it is August 2006 version.
EDIT3: When i change #if D3DX_SDK_VERSION != 30 #if D3DX_SDK_VERSION <= 30
[Updated on: Wed, 10 June 2009 04:15] Report message to a moderator |
|
|
|
|
|
|
|
| Re: Shader Plugin / Shader Help [message #389923 is a reply to message #389917] |
Wed, 10 June 2009 07:50 |
|
Omar007
Messages: 1711
Registered: December 2007
Location: Amsterdam
Karma: 0
|
General (1 Star) |
|
|
| halo2pac wrote on Wed, 10 June 2009 15:46 |
| Omar007 wrote on Wed, 10 June 2009 05:04 |
EDIT3: When i change #if D3DX_SDK_VERSION != 30 #if D3DX_SDK_VERSION <= 30
|
Um is that a good idea?
and if so .. why not just remove the line instead of adding "<="?
|
Actually it comes down to the same point as having to change the _MSC_VER_ == 1400 to _MSC_VER_ <= 1400 in engine_common.cpp (or something) to compile scripts on VC2008.
And i think you could delete the line BUT only if you also delete the 2 following lines otherwise it would ALWAYS give the error you have to change the Delay Load DLL.
I just changed it to #if D3DX_SDK_VERSION <= 30
[Updated on: Wed, 10 June 2009 07:51] Report message to a moderator |
|
|
|
| Re: Shader Plugin / Shader Help [message #389945 is a reply to message #389923] |
Wed, 10 June 2009 10:36 |
|
saberhawk
Messages: 1068
Registered: January 2006
Location: ::1
Karma: 0
|
General (1 Star) |
|
|
| Omar007 wrote on Wed, 10 June 2009 10:50 |
| halo2pac wrote on Wed, 10 June 2009 15:46 |
| Omar007 wrote on Wed, 10 June 2009 05:04 |
EDIT3: When i change #if D3DX_SDK_VERSION != 30 #if D3DX_SDK_VERSION <= 30
|
Um is that a good idea?
and if so .. why not just remove the line instead of adding "<="?
|
Actually it comes down to the same point as having to change the _MSC_VER_ == 1400 to _MSC_VER_ <= 1400 in engine_common.cpp (or something) to compile scripts on VC2008.
And i think you could delete the line BUT only if you also delete the 2 following lines otherwise it would ALWAYS give the error you have to change the Delay Load DLL.
I just changed it to #if D3DX_SDK_VERSION <= 30
|
The *reason* for that #if being exactly the way it was is so that the warning always triggers if you don't have the SDK matching that version number installed. If the DLL file says 41, the D3DX_SDK_VERSION is 41 and the line should be changed to read #if D3DX_SDK_VERSION != 41
|
|
|
|
|
|
|
|
| Re: Shader Plugin / Shader Help [message #390091 is a reply to message #390003] |
Thu, 11 June 2009 01:20 |
|
Omar007
Messages: 1711
Registered: December 2007
Location: Amsterdam
Karma: 0
|
General (1 Star) |
|
|
Toggle Spoiler| Saberhawk wrote on Thu, 11 June 2009 00:05 |
| Omar007 wrote on Wed, 10 June 2009 13:58 |
| Saberhawk wrote on Wed, 10 June 2009 19:36 |
| Omar007 wrote on Wed, 10 June 2009 10:50 |
| halo2pac wrote on Wed, 10 June 2009 15:46 |
| Omar007 wrote on Wed, 10 June 2009 05:04 |
EDIT3: When i change #if D3DX_SDK_VERSION != 30 #if D3DX_SDK_VERSION <= 30
|
Um is that a good idea?
and if so .. why not just remove the line instead of adding "<="?
|
Actually it comes down to the same point as having to change the _MSC_VER_ == 1400 to _MSC_VER_ <= 1400 in engine_common.cpp (or something) to compile scripts on VC2008.
And i think you could delete the line BUT only if you also delete the 2 following lines otherwise it would ALWAYS give the error you have to change the Delay Load DLL.
I just changed it to #if D3DX_SDK_VERSION <= 30
|
The *reason* for that #if being exactly the way it was is so that the warning always triggers if you don't have the SDK matching that version number installed. If the DLL file says 41, the D3DX_SDK_VERSION is 41 and the line should be changed to read #if D3DX_SDK_VERSION != 41
|
True but i changed it to <= 30 so even if i get on a PC with a version between 30 and 41 i still can compile it 
|
But it won't work because the Delay Load settings would be wrong. It was setup to always trigger if the SDK version was different because you can only build versions of shaders.dll that match the version of the SDK installed.
|
I did use that first but as i typed earlier it works also in the way i use it now so it doesnt really matter because it works now too.
*Jumped into my mind:
And wouldnt that it the same for case for the change of to which has to be changed to use a newer VC++ version than 2005.
What i did is actually the same but than for using a newer SDK instead of using a newer Compiler.
EDIT: What version does TT use for scripts 4.0?
[Updated on: Thu, 11 June 2009 01:22] Report message to a moderator |
|
|
|
| Re: Shader Plugin / Shader Help [message #390109 is a reply to message #390091] |
Thu, 11 June 2009 03:03 |
|
saberhawk
Messages: 1068
Registered: January 2006
Location: ::1
Karma: 0
|
General (1 Star) |
|
|
| Omar007 wrote on Thu, 11 June 2009 04:20 |
I did use that first but as i typed earlier it works also in the way i use it now so it doesnt really matter because it works now too.
*Jumped into my mind:
And wouldnt that it the same for case for the change of to which has to be changed to use a newer VC++ version than 2005.
What i did is actually the same but than for using a newer SDK instead of using a newer Compiler.
EDIT: What version does TT use for scripts 4.0?
|
It's not the same case as for the change of the _MSC_VER_ because the DXSDK error was put in there to remind people to look at the project settings and match the SDK version up, whereas the _MSC_VER_ code was put in there to fix issues with the way scripts.dll did things when Visual Studio 2005 SP1 *or newer* was used to compile it.
scripts 4.0 is currently using the November 2007 DirectX SDK
|
|
|
|
|
|
Search
Help
Members
Register
Login
Home
