I remember used hours of time getting all the shaders to compile last time I
messed with them.Can't remember how I fixed it though :-/

/ScarT


2009/2/19 Russ Canfield <[email protected]>

> Well I was able to reinstall the SDK and reinstall all of steam into a
> directory without spaces. Along with the tutorials for minor updates I was
> able to get it to compile. Yay!!! however Walter I think you are onto
> something. All the include files are created, but only one .vcs which is:
>
> SDK_Unlitgeneric_lightingonly.vcs
>
> No other .vcs files were created and I used the script to compile
> mycustomshaders.txt and stdshader_dx8 and 9. The include files are created
> flawlessly. However no .vcs, the makefile for my shaders contains the
> following(from the SDK nightvision tutorial):
>
> default:  "fxctmp9\post_nightvision_ps20.inc"
> "shaders\fxc\post_nightvision_ps20.vcs" "fxctmp9\PassThrough_vs20.inc"
> "shaders\fxc\PassThrough_vs20.vcs"
>
> clean:
>  del /f /q "fxctmp9\post_nightvision_ps20.inc"
>  del /f /q "shaders\fxc\post_nightvision_ps20.vcs"
>  del /f /q "fxctmp9\PassThrough_vs20.inc"
>  del /f /q "shaders\fxc\PassThrough_vs20.vcs"
>
> fxctmp9\post_nightvision_ps20.inc shaders\fxc\post_nightvision_ps20.vcs:
> ..\..\devtools\bin\updateshaders.pl ..\..\devtools\bin\fxc_prep.pl
> post_nightvision_ps20.fxc ..\..\materialsystem\stdshaders\common_ps_fxc.h
> ..\..\materialsystem\stdshaders\common_hlsl_cpp_consts.h
> ..\..\materialsystem\stdshaders\common_fxc.h
>  "..\..\devtools\bin\perl.exe"
> ..\..\devtools\bin\fxc_prep.pl"  -shaderoutputdir shaders -source "..\.."
> post_nightvision_ps20.fxc
>  echo post_nightvision_ps20.fxc>> filestocopy.txt
>  echo ..\..\materialsystem\stdshaders\common_ps_fxc.h>> filestocopy.txt
>  echo ..\..\materialsystem\stdshaders\common_hlsl_cpp_consts.h>>
> filestocopy.txt
>  echo ..\..\materialsystem\stdshaders\common_fxc.h>> filestocopy.txt
>
> fxctmp9\PassThrough_vs20.inc shaders\fxc\PassThrough_vs20.vcs:
> ..\..\devtools\bin\updateshaders.pl ..\..\devtools\bin\fxc_prep.pl
> PassThrough_vs20.fxc
> ..\..\materialsystem\stdshaders\common_hlsl_cpp_consts.h
> ..\..\materialsystem\stdshaders\common_vs_fxc.h
> ..\..\materialsystem\stdshaders\common_fxc.h
>  "..\..\devtools\bin\perl.exe"
> ..\..\devtools\bin\fxc_prep.pl"  -shaderoutputdir shaders -source "..\.."
> PassThrough_vs20.fxc
>  echo PassThrough_vs20.fxc>> filestocopy.txt
>  echo ..\..\materialsystem\stdshaders\common_hlsl_cpp_consts.h>>
> filestocopy.txt
>  echo ..\..\materialsystem\stdshaders\common_vs_fxc.h>> filestocopy.txt
>  echo ..\..\materialsystem\stdshaders\common_fxc.h>> filestocopy.txt
>
>
> I am new to shaders and I hope to learn more about them, if they ever
> compile!! :o)
> Please write back Walter, I greatly appreciate your time helping me.
>
> Thanks
>
>
> ----- Original Message -----
> From: "Walter Gray" <[email protected]>
> To: "Discussion of Half-Life Programming" <[email protected]
> >
> Sent: Thursday, February 19, 2009 3:04 PM
> Subject: Re: [hlcoders] Shaders and ActivePerl
>
>
> > Do you have a makefile.modshaders file in your stdshaders directory?
> > This file is generated by updateshaders.pl and should have a rule for
> > myshader.vcs that looks something like this:
> >
> > fxctmp9\post_screenspace_vs20.inc shaders\fxc\post_screenspace_vs20.vcs:
> > ..\..\devtools\bin\updateshaders.pl ..\..\devtools\bin\fxc_prep.pl
> > post_screenspace_vs20.fxc
> > ..\..\materialsystem\stdshaders\common_hlsl_cpp_consts.h
> > ..\..\materialsystem\stdshaders\common_vs_fxc.h
> > ..\..\materialsystem\stdshaders\common_fxc.h
> >    perl "..\..\devtools\bin\fxc_prep.pl"  -shaderoutputdir shaders
> > -source "..\.." post_screenspace_vs20.fxc
> >    echo post_screenspace_vs20.fxc>> filestocopy.txt
> >    echo ..\..\materialsystem\stdshaders\common_hlsl_cpp_consts.h>>
> > filestocopy.txt
> >    echo ..\..\materialsystem\stdshaders\common_vs_fxc.h>> filestocopy.txt
> >    echo ..\..\materialsystem\stdshaders\common_fxc.h>> filestocopy.txt
> >
> > I would also reccomend reverting all the build files to the state they
> > were in originally, plus the minor tweak to runvmpi.pl if you have
> > spaces in your paths, and double check that your environmental variables
> > are set properly.
> >
> > Russ Canfield wrote:
> >> Ok, so I do not know if I was supposed to but I decided to change all
> >> references to pearl to look in C:\Perl\bin directory. Now I get this
> >> error
> >>
> >> NMAKE : U1073: dont know how to make file "myshader.vcs"
> >>
> >> Stop.
> >>
> >> Ahhhh, anyone know how to fix this? or want to contact me personally to
> >> email me a copy of their 3 SDK shader setup files?
> >> [email protected]
> >>
> >> Thanks!
> >>
> >> ----- Original Message -----
> >> From: "Tobias Kammersgaard" <[email protected]>
> >> To: "Discussion of Half-Life Programming"
> >> <[email protected]>
> >> Sent: Tuesday, February 17, 2009 6:27 PM
> >> Subject: Re: [hlcoders] Shaders and ActivePerl
> >>
> >>
> >>
> >>> Well where did you install Perl to? Do a search for perl.exe and change
> >>> the
> >>> batch to match that location.
> >>> /ScarT
> >>>
> >>>
> >>> 2009/2/18 Russ Canfield <[email protected]>
> >>>
> >>>
> >>>> 1 file(s) moved.
> >>>>
> >>>> ' "C:\Perl\perl.exe"' is not recongized as an internal or external
> >>>> command,
> >>>> operable program or bath file.
> >>>>
> >>>> and continues with the SDK shaders from there.
> >>>>
> >>>>
> >>>> ----- Original Message -----
> >>>> From: "Tobias Kammersgaard" <[email protected]>
> >>>> To: "Discussion of Half-Life Programming"
> >>>> <[email protected]
> >>>>
> >>>> Sent: Tuesday, February 17, 2009 6:15 PM
> >>>> Subject: Re: [hlcoders] Shaders and ActivePerl
> >>>>
> >>>>
> >>>>
> >>>>> This
> >>>>>
> >>>>> perl(.exe) "C:\Perl"
> >>>>> "%SrcDirBase%\materialsystem\stdshaders\runvmpi.pl"
> >>>>> %xbox_args% -changetodir %ChangeToDir% %SDKArgs%
> >>>>>
> >>>>> Attempts to open a Perl script called "C:\Perl" which of course
> >>>>> doesn't
> >>>>> exist.
> >>>>>
> >>>>> Try this instead.
> >>>>>
> >>>>> "C:\Perl\perl.exe"
> "%SrcDirBase%\materialsystem\stdshaders\runvmpi.pl"
> >>>>> %xbox_args% -changetodir %ChangeToDir% %SDKArgs%
> >>>>>
> >>>>>
> >>>>> /ScarT
> >>>>>
> >>>>>
> >>>>> 2009/2/18 Russ Canfield <[email protected]>
> >>>>>
> >>>>>
> >>>>>> I have been trying to compile shaders for the last week...I have
> >>>>>>
> >>>> followed
> >>>>
> >>>>>> every tutorial out there on fixing directories with spaces, and
> about
> >>>>>> everything else
> >>>>>> you could think of for the HL2 SDK...Well I am using
> >>>>>> ActivePerl....and
> >>>>>>
> >>>> my
> >>>>
> >>>>>> code is based on EP1.....
> >>>>>>
> >>>>>> With that being said, I follow this tutorial:
> >>>>>> http://developer.valvesoftware.com/wiki/Shader_Authoring
> >>>>>>
> >>>>>> I follow this tutorial:
> >>>>>> http://www.wraiyth.com/index.php?q=node/5
> >>>>>>
> >>>>>> And when I go to compile I get the following error:
> >>>>>> myps20.fxc...writing inc
> >>>>>> myvs20.fxc...writing inc
> >>>>>> 1 file(s) moved.
> >>>>>> Can't open perl script "C:\Perl" Permission denied.
> >>>>>>
> >>>>>> From there it copies my .fxc files and all the SDK .vcs files
> >>>>>> fine....
> >>>>>>
> >>>>>> I switched the directory it looks for Perl to C:\Perl because thats
> >>>>>>
> >>>> where
> >>>>
> >>>>>> its installed.....
> >>>>>>
> >>>>>> buildsdkshaders.bat was modified with this line:
> >>>>>>
> >>>>>> REM ****************
> >>>>>> REM Execute distributed process on work/build list
> >>>>>> REM ****************
> >>>>>> perl "C:\Perl" "%SrcDirBase%\materialsystem\stdshaders\runvmpi.pl"
> >>>>>> %xbox_args% -changetodir %ChangeToDir% %SDKArgs%
> >>>>>>
> >>>>>> If anyone can help me I would greatly appreciate it. I am so lost,
> >>>>>> and
> >>>>>> I
> >>>>>> know very little about perl. Please help!!!
> >>>>>> _______________________________________________
> >>>>>> To unsubscribe, edit your list preferences, or view the list
> >>>>>> archives,
> >>>>>> please visit:
> >>>>>> http://list.valvesoftware.com/mailman/listinfo/hlcoders
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> _______________________________________________
> >>>>> To unsubscribe, edit your list preferences, or view the list
> archives,
> >>>>> please visit:
> >>>>> http://list.valvesoftware.com/mailman/listinfo/hlcoders
> >>>>>
> >>>>>
> >>>> _______________________________________________
> >>>> To unsubscribe, edit your list preferences, or view the list archives,
> >>>> please visit:
> >>>> http://list.valvesoftware.com/mailman/listinfo/hlcoders
> >>>>
> >>>>
> >>>>
> >>> _______________________________________________
> >>> To unsubscribe, edit your list preferences, or view the list archives,
> >>> please visit:
> >>> http://list.valvesoftware.com/mailman/listinfo/hlcoders
> >>>
> >>>
> >>
> >>
> >> _______________________________________________
> >> To unsubscribe, edit your list preferences, or view the list archives,
> >> please visit:
> >> http://list.valvesoftware.com/mailman/listinfo/hlcoders
> >>
> >>
> >
> >
> > _______________________________________________
> > To unsubscribe, edit your list preferences, or view the list archives,
> > please visit:
> > http://list.valvesoftware.com/mailman/listinfo/hlcoders
> >
>
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>
>
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders

Reply via email to