[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions_content.php on line 1014: Undefined array key 3 [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions_content.php on line 1014: Undefined array key 3 [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions_content.php on line 1014: Undefined array key 3 [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions_content.php on line 1014: Undefined array key 3 [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions_content.php on line 1014: Undefined array key 3 [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4130: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3009) [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4130: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3009) [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4130: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3009) [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4130: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3009) why wont it build? - Battlezone Forums
I can't get this to build what I want it to.
help if you can bcouse at this point I have no idea whats wrong the object it should build can be placed and works in the editer I got buildings like this to work but I just can't get this blasted thing to.
here it is.
MrTwosheds wrote:fbrecy_deploy has a terrain__h, not sure if setting ownsTerrain = 0 is going to be enough to convince it to not be a terrain owning object.
ok I will try a diffrent building model now.
dose not work.
I don't undersand whats wrong.
well I think after this I can see that it will take a lot more work to get this to work.
MrTwosheds wrote:fbrecy_deploy has a terrain__h, not sure if setting ownsTerrain = 0 is going to be enough to convince it to not be a terrain owning object.
Actually, I think it does; it's a trick I use now and again when creating maps that require separate objects to be inconveniently close to one another.
Well if I saw a terrain__h plate owning building occupying the same terrain as another, I would just think it was broken, I cant see why anyone would want to do this.