3D Skybox
Quote from Dafflewoctor on July 14, 2013, 9:10 pmAm I the only person who finds this process extremely confusing? I don't even understand the point of shrinking down your map and making a duplicate.
So I know I've missed steps, but here's what I've done:
1) Created a hollow skybox around my map.
2) Copied all my world geometry + the sky camera and pasted it somewhere else in the map
3) I shunk it down to 0.0625 times its size....and that should be all, right? But all the tutorials for this are extremely confusing.
When I try to compile the map, I get a whole slew of errors, I attached the compile log.
Also, just out of curiosity, could someone please explain how the whole shrinking down thing works?
Thanks in advance.
Am I the only person who finds this process extremely confusing? I don't even understand the point of shrinking down your map and making a duplicate.
So I know I've missed steps, but here's what I've done:
1) Created a hollow skybox around my map.
2) Copied all my world geometry + the sky camera and pasted it somewhere else in the map
3) I shunk it down to 0.0625 times its size.
...and that should be all, right? But all the tutorials for this are extremely confusing.
When I try to compile the map, I get a whole slew of errors, I attached the compile log.
Also, just out of curiosity, could someone please explain how the whole shrinking down thing works?
Thanks in advance.

Quote from ChickenMobile on July 14, 2013, 11:59 pmIt's no wonder you have microbrushes, copying the whole map is not how you make a 3D skybox. The only thing you should be shrinking down is the objects you want to appear in the 3D skybox otherwise it will overlap with already existing brushwork.
The reason you should make the 3D skybox objects first in the large world is because it would then fit perfectly relative to the origin of your map.Brushes in the 3D skybox should be converted to func_detail to avoid creating a bazillion leafs in small 16x smaller space.
It's no wonder you have microbrushes, copying the whole map is not how you make a 3D skybox. The only thing you should be shrinking down is the objects you want to appear in the 3D skybox otherwise it will overlap with already existing brushwork.
The reason you should make the 3D skybox objects first in the large world is because it would then fit perfectly relative to the origin of your map.
Brushes in the 3D skybox should be converted to func_detail to avoid creating a bazillion leafs in small 16x smaller space.
Quote from Tmast98 on July 15, 2013, 12:29 amHey,
Here's a great tutorial made by LpFreaky90, I used it myself and it helps a ton.
There's a link to the video.
Hey,
Here's a great tutorial made by LpFreaky90, I used it myself and it helps a ton.
There's a link to the video.

Quote from josepezdj on July 15, 2013, 2:51 am@Dr.Toaster Waffles: maybe your microbrushes are just very small brushes that you have shrinked turning them into microbrushes
Revise all the brushes you are scaling down. Check out if you used the clipping tool to divide brushes several times in certain angles without noticing you were creating microbrushes (this happens sometimes when you are dividing a glass to make it look like broken and to create its gibs):
[spoiler]
[/spoiler]
Maybe this way you actually made microbrushes, or just small brushes that become micro after shrinking them.Hmmmm.... your map is leaking, have you tried to compile without the shrinkage (without your skybox box)? if it compiles correctly without the skybox box but not with it, that could mean that those microbrushes are surrounding and sealing your skybox box and so when the compile removes them, it leaks... revise those areas.
@Dr.Toaster Waffles: maybe your microbrushes are just very small brushes that you have shrinked turning them into microbrushes Revise all the brushes you are scaling down. Check out if you used the clipping tool to divide brushes several times in certain angles without noticing you were creating microbrushes (this happens sometimes when you are dividing a glass to make it look like broken and to create its gibs):

Maybe this way you actually made microbrushes, or just small brushes that become micro after shrinking them.
Hmmmm.... your map is leaking, have you tried to compile without the shrinkage (without your skybox box)? if it compiles correctly without the skybox box but not with it, that could mean that those microbrushes are surrounding and sealing your skybox box and so when the compile removes them, it leaks... revise those areas.
Quote from Dafflewoctor on July 15, 2013, 7:31 amjosepezdj wrote:Hmmmm.... your map is leaking, have you tried to compile without the shrinkage (without your skybox box)? if it compiles correctly without the skybox box but not with it, that could mean that those microbrushes are surrounding and sealing your skybox box and so when the compile removes them, it leaks... revise those areas.It will fully complie without all the micro-brushes, yes. But I have a hole in my chamber where you can see the skybox, and it seems to suck most of the light out of my map, leaving all my textures black and barely visible.
Also I think that's right about my clipping of brushes creating micro-brushes when I shrink them down. So my question is how do I not create micro-brushes when I shrink down the map without making the original map larger?
If I load my pointfile, it goes to my sky_camera entity in the small map. I don't understand how it's leaked, though, and this happens with any entity I put outside with the exception of some instances-I used the ambient_destruction instance and put it outside my map, but the compile says it's leaked, so I had to build a huge nodraw brush surrounding the instance and my map, which takes my compile five minutes longer.
It will fully complie without all the micro-brushes, yes. But I have a hole in my chamber where you can see the skybox, and it seems to suck most of the light out of my map, leaving all my textures black and barely visible.
Also I think that's right about my clipping of brushes creating micro-brushes when I shrink them down. So my question is how do I not create micro-brushes when I shrink down the map without making the original map larger?
If I load my pointfile, it goes to my sky_camera entity in the small map. I don't understand how it's leaked, though, and this happens with any entity I put outside with the exception of some instances-I used the ambient_destruction instance and put it outside my map, but the compile says it's leaked, so I had to build a huge nodraw brush surrounding the instance and my map, which takes my compile five minutes longer.

Quote from josepezdj on July 15, 2013, 8:53 amYou might have any brush that you think is sealing your map or your skybox box tied to a func_brush or func_detail, check out where the pointfile points out.
If you still can't find the leak, just post the .VMF and we'll take a quick look into it.
You might have any brush that you think is sealing your map or your skybox box tied to a func_brush or func_detail, check out where the pointfile points out.
If you still can't find the leak, just post the .VMF and we'll take a quick look into it.
Quote from boctroy on July 15, 2013, 4:51 pmAs you are talking about skyboxes, i have a question as well, is there anyway to a clouds to the skybox. it seams that portal 2 does not have them.
As you are talking about skyboxes, i have a question as well, is there anyway to a clouds to the skybox. it seams that portal 2 does not have them.

Quote from josepezdj on July 15, 2013, 5:24 pmboctroy wrote:As you are talking about skyboxes, i have a question as well, is there anyway to a clouds to the skybox. it seams that portal 2 does not have them.Yes, the available textures that Portal2 comes with are a bit bland (well, I guess VALVe made the texture they needed for a game that mostly take place into indoors testchambers
)
You can use whatever custom skybox textures you want. There are many at Gamebanana (please don't say they are only for CS, they can be used in any Source game!).
You need to place all textures into your materials/skybox folder (create it if it doesn't exist). And remember to revise each .VMT to make sure it has the following structure:
- Code: Select all
"UnlitGeneric"
{
"$basetexture" "skybox/dreamsdn"
"$nofog" 1
}This means:
a) If at the beginning you see "Sky", change it by "UnlitGeneric"
b) If you find a line that reads "$ignorez" "1", erase it.
The other parameter is the $basetexture, it needs to point out to the path that each of the 6 skybox textures (the 6 faces of a cube) are located
Yes, the available textures that Portal2 comes with are a bit bland (well, I guess VALVe made the texture they needed for a game that mostly take place into indoors testchambers )
You can use whatever custom skybox textures you want. There are many at Gamebanana (please don't say they are only for CS, they can be used in any Source game!).
You need to place all textures into your materials/skybox folder (create it if it doesn't exist). And remember to revise each .VMT to make sure it has the following structure:
- Code: Select all
"UnlitGeneric"
{
"$basetexture" "skybox/dreamsdn"
"$nofog" 1
}
This means:
a) If at the beginning you see "Sky", change it by "UnlitGeneric"
b) If you find a line that reads "$ignorez" "1", erase it.
The other parameter is the $basetexture, it needs to point out to the path that each of the 6 skybox textures (the 6 faces of a cube) are located
Quote from Dafflewoctor on July 15, 2013, 9:18 pm...hmm. Well, I found my problem-I accidentally deleted some lighting in the map and it made the textures all black. Turns out I don't even need the 3d skybox, just a normal one.
But thanks for the info josepezdj, I was wondering how people got cloudy skyboxes in their maps.
...hmm. Well, I found my problem-I accidentally deleted some lighting in the map and it made the textures all black. Turns out I don't even need the 3d skybox, just a normal one.
But thanks for the info josepezdj, I was wondering how people got cloudy skyboxes in their maps.
Quote from Dafflewoctor on January 3, 2014, 12:39 pmI apologize for the superbump of this thread, but it was on the topic. I downloaded a custom skybox from csbanana, and I have this line in some the vmts:
"$basetexturetransform" "center 0 0 scale 1 2 rotate 0 translate 0 0"
Should I delete it or should I keep it?
I apologize for the superbump of this thread, but it was on the topic. I downloaded a custom skybox from csbanana, and I have this line in some the vmts:
"$basetexturetransform" "center 0 0 scale 1 2 rotate 0 translate 0 0"
Should I delete it or should I keep it?