 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
People should use there own nicks and not other�s people nicks...
i dont give a shit about nothing... wrath i didn�t wrote that... so peace! for who is trying to use my nick, get a life... Yeah I agree with Scampbell on a bunch of things too. It's very useful feedback.
Scampbell: What exactly do you mean in the first screen shot about moving the spawn up to the doors? Thanks for the feedback so far everyone. I mean cut the room circled, and put the spawn there. The existing doorways from the room cut into the rest of the map and now the exits from the spawn.
I actually like the circled room, so I might just cut out the regular spawn room and move all the teamspawn there instead.
Megaman just linked to that thing i had in mind: http://de-war.de/eurekacarpark.html
I reached three days full vising.
73.80% Elapsed 23h30m, Left 24h16m Total47h46m, 49%. Nothing happened last two days. http://members.home.nl/gimli/arcus05.jpg http://members.home.nl/gimli/arcus06.jpg http://members.home.nl/gimli/arcus10.jpg http://members.home.nl/gimli/arcus16.jpg The map plays well, and I'm just below the max clip and vertices. Only on fast vis, or I'll wait for years. http://members.home.nl/gimli/arcus16.jpg
I think I see the source of your trouble. Tell me those railings are a func_wall? Then what's taking days upon days of VIS time? Is your computer older maybe? Nothing else in those shots looks particularly VIS unfriendly...
The map is rather big (8Mb) and fast vis takes no time.
R_speeds are extremely high. I used no func walls, and hardly vis blokkers. hey madfox nice theme and you've got some nice construction here but the texturing could use a lot of work. if you can't get those big bricks ending in the right place, then i'd use much smaller bricks so you don't notice when they get cut in half. in acrus10.jpg for instance, almost every brick gets cut in half at the edge, which ends up looking sloppy. also things like underneath archways and ceilings don't need to be the same brick texture. the railings i think wood look better in wood too.
I crawled out of this map construction with my first suceedment of texture alignment. And as it was the first mistake I never saw in mapping
I experience it as a small improvement. My first goal was to make the map excist without homs or max warnings. Reason why I had to take advantage of the mdl files. And as the texture count grows on 72 it still could have some more archivement. I'm now on a P4 3Ghz and I never had a longer vising count than 8 houres. After boxing the map the vistime just raised dramatical. And I can't delete that because the map immedeately starts leaking. Are you trying to beat the CDA fullvis runtime ? :P
Wide open area needs long time to compile, and regarding the shots, it looks awesome, plenty of details everywhere... You will certainely have to wait for almost the same time before seeing a 100% fullvised map... Anyway, good luck, be patient, and we all hope to see the release soon.. Keep it up ! After boxing the map
are you saying you built a giant box around the entire map to get it to vis? because that would certainly explain why it's taking so long. Oh yeah, OK, if you can't get it to VIS without boxing that would explain your VIS times. Having the process all of the outside stuff that QBSP would normally cull away will double or triple your VIS times easily.
And on the road the map has crossed was a point where the box wasn't necessary to compile it, but then the max limit was reached and it had many hom's.
but that map ended on a burned out mobo, so make my cahsbox smile.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |