Decompile Problem Created 17 years ago2007-10-27 16:39:06 UTC by Striker

I want to modify some maps.Ok I know not all the solids will be loaded "due to the errors" but that isn't a problem.The real problem is that when I open hammer all the textures are only colors- dark yellow(in dust for example) ,grey(in cs_assault) or any other colour that is looking like the texture.

The REAL problem? I can't retexture the walls !!! It doesn't matter what texture I'm Using,all are just colors.

How can I fix this?

Did you check other maps to see if it's the same way?

Other than that, do you have all the necessary wads loaded?

Yes. I have cs_assault , halflife.WAD ,cs_dust.WAD and some textures made by me.And not only de_dust has that problem.I tried to decompile ka_allinlone

or what name it has to show something on the forum and it was the same problem.And anothetr thing:

There is a little thing called "textract" .It extracts textures from the maps.But do you know how to use this tool?

If you use it, it should just put a wad in the output folder.

Do any of your homemade maps do the same thing?

this is normal for a decompile. decompile carves the map from a giant cube, resulting in lots of invalid brushes. it also makes it impossible to recompile from the decompiled map, but its good to see how some entity setups were done.

Actually, BSPTwoMap does it a little different, hollowing out all the brushes. The annoying thing is, this was actually intentionally implemented as a way to keep people from accurately decompiling maps. Otherwise, you might have been able to pull it off.

Not sure about the texture thing though...that's really strange, and I don't think I'd call it normal. It sounds almost like you have "3D Filled Polygons" turned on in your view menu.

decompilers fuck everything to shit.

Try pressing Alt+P and look for texture-errors, usually the texture-scaling get f*cked up when decompiling(just like everything else in the map).

Ok i'll show you a screen shot in a few moments...

and it isn't set to "filled poligons"

P.S. I decompiled ka_roadwars_v2 here

Not sure, but this happens when the map has wad's included in the bsp.

Try this:

Extract the textures from the bsp using Textract.
Put all these textures into a new wad and load it into Hammer.
Then decompile the map and load the map in Hammer.

If you still see flat colors all over the place, then BSPTwoMAP can't handle bsp files that have wads included in them.

Whats the point of this anyway?

The point is that I want to modify cs_assault.

The problem is that I don't know how to handle Textract. When I open the program it just shuts down immediately.I have to do it another way?

The point is that I want to modify cs_assault.

Right... And then what? Release it? Thats stealing, you know.

The problem is that I don't know how to handle Textract. When I open the program it just shuts down immediately.I have to do it another way?

Its probably a command line application, check the application readme file for correct usage (which is pretty much common sense).

The point is, there is no way to "modify" cs_assault, because it would entail REBUILDING the whole thing.

I've made my own version of cs_assault before, as have many people. I would not suggest simply "modifying" the original. I would suggest making your own.

hmmm.....my "readme" file is in german

well I think it's to difficult to build the assault from 0 ....and many .many people modified the cs_assault map.You can't say it isn't true.......And as I saw those maps....well ...all are just modifications(and I have a lot of cs_assault maps) Big modification or tiny modifications.Not from 0.

Actrully this is a very interesting problem. This happened to me when I ported over a very old map from worldcraft 2.1 to hammer 3.5. I wasn't able to fox the problem.

they dont modify, they decompile and use that as a reference to rebuild.

Don't revive old threads.