James Luke...what did the Xash3D "steal" from Valve to make that company so angry.IIRC, Xash3D and other sorts of projects that use it had code from the 2003 HL2 leak. Which is deemed illegal to use by Valve, and for good reason.
how about I post a video insteadWell that was sudden...
https://www.youtube.com/watch?v=dousurwwElI
many of the core game mechanics simply cannot translate into goldsource.You'd be surprised what you can do with coding and a little bit of patience.
-snipHaving a look through the code, 'LoadCacheTexture' is used in 'SetupSpotLight', and it has a clamp argument.
{
gl.glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP );
gl.glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP );
}[/quote]They're the same thing. HL solved switchable lights by providing up to 4 lightmaps stored in the BSP per surface:I'm guessing there aren't many workarounds? If none?
1 - Base inanimate lightmap
2, 3, 4 - Lightmaps containing light colors for each light that affects the surface. This can be both switchable lights and animated lights. Paranoia uses this slot to store it's bump map data, thus why switchable lights aren't supported.
Custom light styles are not supported in any way by Paranoia, because as I said earlier, Paranoia's hlrad hijacks that to put bump map data alongside the normal lighting information.Sorry, I meant toggle lights, not dynamic light styles.
As for the hacked dll, Paranoia I believe only uses it to set certain bits in the pixelformadescriptor for alpha and stencil bits, and to hack the depth range for the skybox they have, and to clear bits at the frame start. I can explain how it's used exactly.That would be great, I want to see if I can fix it in the solution for the source that came for the '.dll'.
I never needed it because I rendered stuff properly, and didn't need ugly hacks, snipWith the way you properly render it, I might be able to do that by changing around some of the calls around. Hopefully it won't require me to add a whole lot of custom code. Any idea how to do the texture tiling thing you were talking about? I don't know much about OpenGL, just a little C++.
You could go on and fix Paranoia's renderer, but unless you want bump maps and specular lighting, it's not worth the effort. Also, you're likely to experience performance issues if you increase the detail in your levels, as a lot of the rendering code is extremely unoptimized.Yeah, I'd have no idea how to optimize it, there's just code leaking everywhere. Everything seems to topple over and crash and burn whenever removing 1 thing or another. I had to remove the sky-box code to be able to play the game without seeing the sky-box flicker out 5 feet in front of me.
The shifting occurs because Paranoia's renderer automatically adjusts the flashlight size based on distance to the nearest wall. This is handled in the code that also sets up the flashlight.'view.cpp' handles the function 'SetupFlashlight', you're right, it does shift and twist based on distance nearest to a wall.
Paranoia never implemented support for detail textures or decals on anything but the worldspawn, so you won't get that working without modifying the rendering code itself.I kind of assumed that based on what I'm finding in the code, I think you have to put in a special entity that will change the custom light style.
I fixed this in Trinity, but porting the code would require some effort. This thing actually contains a lot of fixes that could be applied to Paranoia, but the code was changed substantially.I have used Trinity in the past before, but it is very buggy for me. I decided to have a download of it and I see what you mean by being 'changed substantially'
Can you show an example of transparent objects being messed up? Also the engine you're using won't support switchable texture lights, because Paranoia's renderer overrides that functionality to implement bump maps and such.It's not really so much as a bug as it is a nuisance, basically in game, say when you pick up your suit, the glass doesn't appear to be shaded in with the rest of the environment, might be a lack of the proper RAD that Paranoia's compilers use.
As for changing the name of opengl32.dll, that will disable the renderer entirely I believe. Paranoia used a lot of hacky methods that needed the stencil buffer, etc, and it was programmed to disable itself if it's missing. The hacky opengl32.dll acts as a bridge between Half-Life and the system's actual dll, overriding certain values sent to the GPU. If you rename it or take it out of that folder, it won't work.I've talked to some of the developers and people who know the engine very well and your right, Paranoia uses a hell of a lot hack-y methods to display their effects. I think a lot of my bugs come from working around the VAC system. Because when Paranoia loaded the library, they used 'opengl32.dll', since hackers used this upload cheats into Half-Life later on, Valve removed the ability to have it. So, to overcome this, I had to rebuild and rename 'opengl32.dll' to 'opengl32wl.dll' to work around that.
I heard of people playing Paranoia in multiplayer with the hacky dll in place, and VAC didn't ban them, but I wouldn't bet my life on it. Maybe someone else can confirm this?Same, I haven't tried it because I value my Steam account, but I think not having the hack on you can play some multiplayer. I heard it was a lot of fun to use the snipers, but I'm not so sure.
And according to the SoHL 1.9 source code I've found, you should have this code :So the glDepthMask(1) and the _asm and all that in the if r_shadows == 1? I tried that and it doesn't work.
if (CVAR_GET_FLOAT("r_shadows") == 1 && gEngfuncs.GetViewModel() != m_pCurrentEntity)
{
DrawShadows();
}
Replace "DrawShadows();" by the original code (which is the glDepthMask(1); and assembly code).
GL_StudioDrawShadow = (void(*)(void))(((unsigned int)IEngineStudio.GL_StudioDrawShadow) + 32); if (CVAR_GET_FLOAT("r_shadow") == 1 && gEngfuncs.GetViewModel() != m_pCurrentEntity)
{
glDepthMask( 1 ); _asm
{
push ecx; jmp [GL_StudioDrawShadow];
}
}Can you run the mod through Visual Studio's debugger and tell me on which line it crashes?I haven't set up debugging in my mod, but when I did and ran it with the 'r_shadows' code. I looked through the debug log and this is all I can really find.
snip snipThere's a lot more to the log; here's the full: http://pastebin.com/mBFYxskY
The thread 'Win32 Thread' (0x26b4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x284) has exited with code 0 (0x0).
GL_SIZES: r:8 g:8 b:8 a:0 depth:24
snip snip
First-chance exception at 0x028a6a10 in hl.exe: 0xC0000005: Access violation writing location 0x00000000.
snip snip
Right click on the client project, Properties, go into the Linker section and Input sub-section and add "opengl32.lib" to the additional dependencies. Clean the solution and build again.That at least made me compile the solution, thanks. But testing it inside of the game, it freezes up and crashes.
snip snipI understand that doing that and getting it to work will make it only Windows, but most people use Windows anyway. Also, about the OpenGL, I'm sure just about everyone with a modern-ish computer uses OpenGL to run Half-Life.
Note that using any OpenGL operation will prevent your mod players from using the software or DirectX renderers. Also the changes you made look quite Windows-specific, so you won't be able to build OSX or Linux versions of your mod with that code. Additionally if you're not incredibly familiar with programming, you're going to have a very difficult time implementing anything complicated using OpenGL.
snip snip
CVAR_CREATE("r_shadows", "0", FCVAR_ARCHIVE );(StudioModelRenderer.cpp)
#include <windows.h>(StudioModelRenderer.cpp)
#include <gl\gl.h>
#include <gl\glu.h>
glDepthMask( 1 );_asm
{
push ecx; jmp [GL_StudioDrawShadow];
}