Alliedassault - View Single Post - New map update

Ydiss · 04-21-2003, 01:39 AM

[quote="Bazooka_Joe":f9c7c]12 hours to compile!!? Holy shiz nit! Hrm. . .are you doing anything to piss off MOHRadiant, like custom textures, or cutting down on any of the geometry? That's a long time, man. Well, so far it looks GREAT, and I wish you the best of luck. I'll move this and leave a copy here.[/quote:f9c7c]

No custom textures, geometry is pretty smart and ordered (I never use CSG subtract, nor hollow and only overlap brushes when I absolutely have to, which is rare). Nothing to cause the VIS tree to clog up like it is.

It doesn't make any sense at all... All evidence points to this new map to compile faster than dmxfire. Less numportals, fewer faces and brushes way fewer static models (like 59 compared to 250+).

I've used detail brushes extensively.

The map only has 240k vis data (dmxfire has 330k+).

dmxfire takes 1 hour no more to compile on my new machine.

I abandoned my new map's compile process after it had been stuck on 99% VIS for 5 hours.

I'm going to spend this week (well, if all goes well hopefully just one night) on debugging the map.

That is I'm going to make copies and start deleting chunks of it to see if there's a particular area causing this issue.

Other than that, I'm not sure what to do... I can't add any more detail brushes or I may as well just not bother trying to VIS at all and the map would be slow as shit to play.

I'll need a lot of that luck, I'm afraid cry:

	(#18)
Ydiss is Offline Senior Member Posts: 2,377 Join Date: Jan 2002 Location: Nottingham, England	04-21-2003, 01:39 AM [quote="Bazooka_Joe":f9c7c]12 hours to compile!!? Holy shiz nit! Hrm. . .are you doing anything to piss off MOHRadiant, like custom textures, or cutting down on any of the geometry? That's a long time, man. Well, so far it looks GREAT, and I wish you the best of luck. I'll move this and leave a copy here.[/quote:f9c7c] No custom textures, geometry is pretty smart and ordered (I never use CSG subtract, nor hollow and only overlap brushes when I absolutely have to, which is rare). Nothing to cause the VIS tree to clog up like it is. It doesn't make any sense at all... All evidence points to this new map to compile faster than dmxfire. Less numportals, fewer faces and brushes way fewer static models (like 59 compared to 250+). I've used detail brushes extensively. The map only has 240k vis data (dmxfire has 330k+). dmxfire takes 1 hour no more to compile on my new machine. I abandoned my new map's compile process after it had been stuck on 99% VIS for 5 hours. I'm going to spend this week (well, if all goes well hopefully just one night) on debugging the map. That is I'm going to make copies and start deleting chunks of it to see if there's a particular area causing this issue. Other than that, I'm not sure what to do... I can't add any more detail brushes or I may as well just not bother trying to VIS at all and the map would be slow as shit to play. I'll need a lot of that luck, I'm afraid cry: