Custom Buildings/ Cities spawned in over each other

[ftshill]

On my server all of the custom cities have spawned in twice. There is no visual impact, however when trying to open a door you have to open it multiple times in order to enter. I presume this is due to the server reading the spawn command in two different locations however I do not know where!

Any help would be awesome. 

 

My custom buildings are kept in the:

 

 vilayercodecustom\dayz_epoch\buildings\ : http://prntscr.com/37rprn

 

\dayz_epoch\init\server_functions.sqf. : http://prntscr.com/37rpcl

 

As you can see in this screenshot: http://prntscr.com/37rrxp the doors of the fire-station open and reveal more doors. This only applies to the custom buildings, not the default. This issue has also only just started happening

 

 

[insertcoins]

that might be the weirdest way I have ever seen to add custom buildings.

[insertcoins]

If the buildings are being created twice, it is most likely at the server and then as the client joins. To solve this simply:

call the addbuildings.sqf from init.sqf within the isServer section.

 

Thanks go out to axeman for that one ^^

 

[PPrimezz]

can you explain it more with details

[ruubje11]

A picture that explains it the best:

 

http://prntscr.com/38dvb1

[cen]

Call them from your server pbo :D

[ruubje11]

Yeah, that works for me as well cen, but that is what he was doing. The way on the screenshot could also make it work and the buildings would still be on the server side so no mission file size change

[JediChris816]

Anyone obtained the fix for this on ther server.pbo?

 

It seems the server_monitor.sqf is streaming objects twice which is what causes the double doors/buildings...

[cen]

or your sqf file is wrong :D

[JediChris816]

or your sqf file is wrong :D

Nah...my custom addons have been working fine up until I made a new build.  Even using the same sqf's in a previous build work fine.  The objects are being streamed twice.  No worries, I've since ditched that build and began another.  There was something in my mission file causing the problem, I just counldn't find it and decided I wasn't going to waste any more time looking for it. I spent almost 20 hrs over the weekend troubleshooting it, then made a new build in an hour using clean files.   :P

[cen]

Yea I find it easier to start over a lot of times too haha