Please or Register to create posts and topics.

An appeal to all mappers - bspzip!

PreviousPage 4 of 4

Thats a good workaround. Nice one aldez

Ald?z wrote:
http://wiki.thinkingwithportals.com/wiki/Publishing_A_Map

Quote:
Warning: If you add an .ain to your .bsp, you'll run into the issue where the .bsp is always now 'later' than your .ain file, and will recompile the node graph first time you run the map from the package. The way around this is to make sure your .ain file is 'newer' than the .bsp you're adding it to. You do this by moving your clock forward (go a year ahead since every time the .bsp is unpacked it creates a new timestamp) before you generate the .ain file, then move the clock back before adding it to your .bsp.

I did that! It didn't work! Actually it worked the first time I did it I think (when I WROTE the above quote) but since then it won't take. I even moved the clock up a year. Could it be because I moved the map from it's original compile location?

Edit: I would be less annoyed about this if I hadn't spent 4 hours on this last night AND hadn't wrote the page on Publishing.

So THAT'S how you do that!

I don't know what to do. You can't put the ain file in a bmz, since it needs to be in the "graphs" folder. I know there are programs that can change the date of a file, but I have never tried any of them. I don't think it isn't a big problem though, especially since the message only is displayed once.

EDIT:
Ignore what I said above. Try this and see if it works:

1) Make sure that the node graph is up to date.
2) Quit Portal
3) bspzip all your files with pakrat (including the ain file). Don't forget to adjust the path.
4) Replace the previous bsp file when you save the new one in pakrat
5) Remove the corresponding ain file in the ".../maps/graphs" folder
6) Done. You should not get the message about rebuilding the node graphs. I have not tried to import the map as a bmz, but I don't think Portal will update the file dates when they are imported.

PreviousPage 4 of 4