Forum posts
The heightmap is what's used to generate a normal map. It tells whatever normal map program you use what parts are supposed to stick out (the white bits) and what dips in (the black bits), and converts it all to the funny blue normals. You won't need one in there with your textures. I'm guessing ShaderPro does this bit all by itself.
Anyway, the fact that your light formation rotates with the texture makes me think it is the normal map doing it, it will need to be evened up so there are no obvious dips in the height map and final normal. I can try it, but not until tonight once I get home from work.
Anyway, the fact that your light formation rotates with the texture makes me think it is the normal map doing it, it will need to be evened up so there are no obvious dips in the height map and final normal. I can try it, but not until tonight once I get home from work.
Actually.. I do see that now. This honestly has me quite stumped.
Try rotating the texture 45 degrees (or something a fair bit off), if the "petal" formation shows up in the exact same position, then I'm willing to bet it's Source's lighting playing up.
EDIT:
This might be the cause, and I can't believe I never thought of it before.
This is the heightmap for the normal, ShaderPro would've generated something similiar based off the diffuse texture. You'll notice some areas come out darker than others, which would end up being deeper, and therefor letting more light 'in'. It just seems very exaggerated.
I'll try evening up the heightmap tomorrow and compiling a new normal map, see how that goes. It could be the problem, but we'll see. If it is the case then the normal maps and Source's lighting are actually doing what they're supposed to be doing.
"normal" "1"
"nocompress" "1"
Which told it to convert it to the appropriate format for normals, and to completely bypass nice filtering/compression. Makes the file large, but gets rid of any artifacts people sometimes get with their bumpmaps.
Try rotating the texture 45 degrees (or something a fair bit off), if the "petal" formation shows up in the exact same position, then I'm willing to bet it's Source's lighting playing up.
EDIT:
This might be the cause, and I can't believe I never thought of it before.
I'll try evening up the heightmap tomorrow and compiling a new normal map, see how that goes. It could be the problem, but we'll see. If it is the case then the normal maps and Source's lighting are actually doing what they're supposed to be doing.
Could that be the reason that you were unable to open my vmt files?Well, they are, but I don't imagine they're the reason I couldn't open them. I would have probably received some sort of syntax error for that.
Are quotations actually necessary?
So how did you made and compiled your normal map texture and used no compression?I used the original vtex.exe method, with a targa and a txt file defining how to create the vtf. The txt simply had:
"normal" "1"
"nocompress" "1"
Which told it to convert it to the appropriate format for normals, and to completely bypass nice filtering/compression. Makes the file large, but gets rid of any artifacts people sometimes get with their bumpmaps.
Finally got around to this, sorry it took a while.
I could open all your .vtf files, but for some reason the .vmt's wouldn't work. Like they were corrupted or something, I'm not sure.
Anyway, I did up new material files and recompiled the map with them, and I had to manually compile a new normal map because I remembered that Nem removed the "No Compress" flag, for some reason.
It turns out the lighting is absolutely fine with HDR enabled, but goes awry when it's off (I scaled the bumpmap up so it's more noticable):
To me, this says the materials aren't the problem anymore. I'll keep looking into it, but I guess I now know this has something to do with the way LDR lighting works with normal mapping in the engine. Restricting users to HDR isn't exactly great.
Anyway, here's the new ones I did up with no compression, just incase you wanted them. They go in materials/temp like your originals.
I could open all your .vtf files, but for some reason the .vmt's wouldn't work. Like they were corrupted or something, I'm not sure.
Anyway, I did up new material files and recompiled the map with them, and I had to manually compile a new normal map because I remembered that Nem removed the "No Compress" flag, for some reason.
It turns out the lighting is absolutely fine with HDR enabled, but goes awry when it's off (I scaled the bumpmap up so it's more noticable):
Anyway, here's the new ones I did up with no compression, just incase you wanted them. They go in materials/temp like your originals.
I cannot think of anything else to say except:
Sigh.
Sigh.
I'll give it a look over.
And the results are still the same? If so, it's probably not the compression at fault.
Delete the light sources, replace them, recompile, then type:
sv_cheats 1
mat_reloadallmaterials
It'll refresh everything, including the lightmaps. If that doesn't work then I'm not really sure what's going on. Would you mind posting the .vmt up here? It might help (or it might not).
Delete the light sources, replace them, recompile, then type:
sv_cheats 1
mat_reloadallmaterials
It'll refresh everything, including the lightmaps. If that doesn't work then I'm not really sure what's going on. Would you mind posting the .vmt up here? It might help (or it might not).
Yeah, I can't say I like where mapping seems to be heading with games lately. All the effort, skill and imagination is being taken out of it, which is really a shame.
Check the compression on your normal map. For the best results normal maps should use either fine compression, or no compression, but this can make the _normal.vtf file quite large. I've noticed that normals that are too heavily compressed can throw lights out wierdly, you might notice the normal comes out perfectly in one direction, but artifact-y and uneven in a different direction.
There's a flag you can use when compiling your textures, I'm assuming you're using VTFEdit to do so?
Tick "No Compress" and make sure you import your normal with a suitable image compression, RGBA8888 will give the nicest (and largest) result, but the others should work ok with No Compress.
Also.. Parallax Mapping is ugly as sin.
There's a flag you can use when compiling your textures, I'm assuming you're using VTFEdit to do so?
Tick "No Compress" and make sure you import your normal with a suitable image compression, RGBA8888 will give the nicest (and largest) result, but the others should work ok with No Compress.
Also.. Parallax Mapping is ugly as sin.
I'll stick with Sven Co-op 3.04.0 is nearing completion, apparently. ;o
Decay on PC, sweet. downloads
Metroid Prime Corruption and Resident Evil 4: Wii Edition both shine with the Wiimote, they're a helluva lot of fun. Gets a little gimmicky after a while though, Wii desperately needs something more hardcore with more depth.
FileFactory
RapidShare
Badongo
None of those require you to sign in/up, which is always handy for lazy people like me.
RapidShare
Badongo
None of those require you to sign in/up, which is always handy for lazy people like me.
Well then you'll have 30+ days to polish your map to perfection. 
Thanks.
Oh right, yeah that should still be the same for Source. Muzz is correct.
So yeah, you'll just have to edit the rad file.
So yeah, you'll just have to edit the rad file.
I tried all the white textures, but all of them gave too much light. Perhaps there is a way to adjust the light setting that a certain texture gives?You need to use the lights.rad file, but that means you'll have to include it as custom content with your map.
I'd try experimenting with standard lights, or decompiling Valve's original map and see whatever they did.
How about you shut the hell up because we all know you don't do a damn thing in favour of TWHL.
You could try it with a point_template. Add all the entities required for the train into one point_template, kill off the existing entities when the train has passed, then trigger the template entities after however long you want. It should work, I think.
This should help, just because it partially shows how to use the point_template.
I'd try making an example map myself, but I'm on a mapping hiatus.
This should help, just because it partially shows how to use the point_template.
I'd try making an example map myself, but I'm on a mapping hiatus.
Ah, well I seem to recall there being a couple of the white texlight textures, maybe there's one in there with the correct lighting. I might be mistaken though.
Valve's original map probably had the window light filtering in from a skybox, not a white texlight. It's a nice light blue, rather than plain white.
Closer inspection leads me to believe they simply placed weak lights near each window. You can see the radial lighting on the ceilings above each window. Makes sense really, now that I remember the outside lighting is actually orange.
Their spotlights also have a slightly more yellow tinge, which contrasts (only slightly, but it works well enough) against the blue.
My advice is, whenever possible, avoid plain white lighting. Giving your light_spots (and the env_spotlights) a subtle yellow/green/blue tinge to suit the environment does a lot for the atmosphere.
Closer inspection leads me to believe they simply placed weak lights near each window. You can see the radial lighting on the ceilings above each window. Makes sense really, now that I remember the outside lighting is actually orange.
Their spotlights also have a slightly more yellow tinge, which contrasts (only slightly, but it works well enough) against the blue.
My advice is, whenever possible, avoid plain white lighting. Giving your light_spots (and the env_spotlights) a subtle yellow/green/blue tinge to suit the environment does a lot for the atmosphere.
Of course the entity work involved would be ultimatly, mind-bendingly fucked up the arse.That's the best kind of entity work.
Correct.
They're seperate. The headcrab might be a model attachment. I'd just try positioning a headcrab ragdoll on the dynamic zombie and parenting it, it should work.. I hope.
Someone who's been around longer than you.
Yep. It's the authors tutorial, so he can do what he likes with it.
Site exclusivity would still be nice, though.
Site exclusivity would still be nice, though.
This thread is dangerously close to being locked.
No problem. I think I've only ever used it once or twice myself, but I can see it being pretty useful.
Spore care factor: zero.
You could try using an env_render to toggle the appearance of the cones.
Magic hallway.
do you think it is right to turn it on given that there is a risk of annihilating the world?Science fiction might make people believe that, but I'm actually interested in what kind of discoveries we'll make with this thing.
Meh, anyone who took the movie too seriously, and hated it as a result, is an idiot. It has to be said. It's impossible to take a movie about giant transforming robots seriously, no matter how well made it is, so why should the film be serious?
It's the perfect example of a pure popcorn flick. I think some people have trouble just sitting back and having fun.
It's the perfect example of a pure popcorn flick. I think some people have trouble just sitting back and having fun.
Basically it's Armageddon/Independence Day/etc.- ie a big dumb disaster flick- with robots thrown on top of it.That is exactly right, and there's nothing wrong with big dumb flicks. It's nothing revolutionary, but it's nothing offensive or vulgar.
I don't understand why people thought it was so amazing. Plus Shia Labeouf is a fucking toolbag, period.Very hard job for me to find people who would actually call the whole movie amazing, it's just loud, silly fun. And I like Shia myself.
Hope to hell the GIJOE movie is better.Directed by Stephen Sommers? No chance in hell.
I've heard of that rumour, Tito. The problem is I think two of the Constructicons have had their name used in the first film. Easy to fix, yes, but still.
I've also heard rumours of "The Fallen" making an appearance (makes sense considering the title), even though he's from the much, much newer generation of Transformers.
My bro's a bit of a Transformers nut, he has all of the original show on DVD and the original animated film too. I guess that's why I know more about Transformers than I thought I did. ;D
I've also heard rumours of "The Fallen" making an appearance (makes sense considering the title), even though he's from the much, much newer generation of Transformers.
My bro's a bit of a Transformers nut, he has all of the original show on DVD and the original animated film too. I guess that's why I know more about Transformers than I thought I did. ;D
He really is, but i'll be damned if Transformers wasn't one the most entertaining brainless action flicks of 2007.
I give this update my tick of approval! I was the 'beta' tester and the new features rock. Solid program, so damn useful.
I know Blaz still frequents the Mapcore forums, mostly doing Source work now. Not sure about the other two.
I will eat a steak so long as it is simply cooked! I don't really care how well done it is, but if you put mushrooms or onions on it, you're getting a steak in the face.
Yes, the transparency is handled entirely when you make the materials, it will appear transparent on the brush, which you can tie to any entity you like.
Err, yes. Yes I do. >_>
I haven't worked with Spirit in ages, but I'm assuming there has to be a flag or parameter somewhere there that can disable that behaviour. It seems strange that Spirit would alter an original entities function without giving you the ability to revert it..?
Also, I'm with Blitzkrieg, unanimous objects gawking at the player sounds hilarious, include a secret one!
Also, I'm with Blitzkrieg, unanimous objects gawking at the player sounds hilarious, include a secret one!
What game is this for, CS:S, TF2? Wouldn't make much difference anyway, but it's always nice to know these things. ;>
That error usually does mean the spawn area is too cluttered, or going through geometry in my experience. The spawn entities origins (the point at the bottom of the Gordon model that always lines up to the grid) should be fine touching the ground, though I usually leave mine 8 or so units above it to be safe.
Also check that your spawn points aren't too close to each other, or objects. Leave, say.. ~32 units of space in each direction around each spawn entity, just to be sure.
That error usually does mean the spawn area is too cluttered, or going through geometry in my experience. The spawn entities origins (the point at the bottom of the Gordon model that always lines up to the grid) should be fine touching the ground, though I usually leave mine 8 or so units above it to be safe.
Also check that your spawn points aren't too close to each other, or objects. Leave, say.. ~32 units of space in each direction around each spawn entity, just to be sure.
Joel Nielsen - [Black Mesa #03] - We've Got Hostiles (Topside)
At this risk of sounding too much like Penguinboy, I will say this:
Only stupid suggestions are refused.
Anything that isn't answered is usually taken under consideration. We've said it a million times, but Penguinboy is very busy and can only dedicate a small amount of his personal time to working on TWHL.
We have a whole list of things to be addressed, so.. patience.
Only stupid suggestions are refused.
Anything that isn't answered is usually taken under consideration. We've said it a million times, but Penguinboy is very busy and can only dedicate a small amount of his personal time to working on TWHL.
We have a whole list of things to be addressed, so.. patience.
Editing bumps threads.
First web standards, then peace between man and animals, and now alcohol.
What's next?
What's next?
I will join shortly if anyone is up for easy kills!
You could just put "sky" in the material browsers filter and find one yourself.
Erm, everyone who just spoke in favour of it, and any web developer with half a brain.