Jump to content
Sign in to follow this  
eagledude4

Strange issue with BinPbo not including p3d

Recommended Posts

I'm experiencing an issue with BinPbo where the p3d in the addon source will not be included in the binarized pbo randomly. When I say randomly, I mean that using the same file with the same BinPbo options, the file will sometimes be included, and sometimes it wont.

I compared the logs of each instance and what I've found is "</model>" isn't found in the .log when the .p3d wasn't included.

Here is the end of my .log file for when the .p3d was included:

Warnings in p:\ed4\ed4_vehicles\civilian\cars\bugatti_veyron\veyron.p3d:VIEW_CARGO
</model>
Creating texture headers file...
23 texture headers saved to file "C:\Users\Jordan\AppData\Local\Temp\ARMAaddons\ed4_vehicles\texHeaders.bin"
w:\C_branch\Poseidon\Arrowhead\El\FileServer\fileServer.cpp(2513) : Assertion failed 'req->RefCounter()==1'

and here's the log file for when it was not:

Creating texture headers file...
23 texture headers saved to file "C:\Users\Jordan\AppData\Local\Temp\ARMAaddons\ed4_vehicles\texHeaders.bin"
w:\C_branch\Poseidon\Arrowhead\El\FileServer\fileServer.cpp(2513) : Assertion failed 'req->RefCounter()==1'

One of the times It succeeded in adding the .p3d, the log had this:

Warnings in p:\ed4\ed4_vehicles\civilian\cars\bugatti_veyron\veyron.p3Convert model p:\ed4\ed4_vehicles\civilian\cars\bugatti_veyron\veyron.p3d -> C:\Users\Jordan\AppData\Local\Temp\ARMAaddons\ed4_vehicles\civilian\cars\bugatti_veyron\veyron.p3d
d:11000
</model>

This is the .dep when the p3d is included:

+p:\ed4\ed4_vehicles\civilian\cars\bugatti_veyron\veyron.p3d
+p:\ed4\ed4_vehicles\civilian\cars\bugatti_veyron\model.cfg
-p:\ed4\ed4_vehicles\civilian\cars\bugatti_veyron\veyron.cfg
-p:\ed4\ed4_vehicles\civilian\cars\bugatti_veyron\bugatti_veyron.cfg
-p:\ed4\ed4_vehicles\civilian\cars\cars.cfg
-p:\ed4\ed4_vehicles\civilian\cars\model.cfg
-p:\ed4\ed4_vehicles\civilian\civilian.cfg
-p:\ed4\ed4_vehicles\civilian\model.cfg
-p:\ed4\ed4_vehicles\ed4_vehicles.cfg
-p:\ed4\ed4_vehicles\model.cfg
-p:\ed4\ed4.cfg
-p:\ed4\model.cfg
-p:\p:.cfg
-p:\model.cfg
-model.cfg
-ed4\ed4_vehicles\civilian\cars\bugatti_veyron\textures\nodamage.paa
-ed4\ed4_skins\data\rvmats\skin.rvmat
-ed4\ed4_skins\data\rvmats\chrome.rvmat
-ed4\ed4_skins\data\textures\grille1.paa
-ed4\ed4_vehicles\civilian\cars\bugatti_veyron\textures\lights.paa
-ed4\ed4_skins\data\textures\undercarriage.paa
-ed4\ed4_vehicles\civilian\cars\bugatti_veyron\textures\wheel.paa
-ed4\ed4_skins\data\textures\tirea0.paa
-ed4\ed4_skins\data\rvmats\glass.rvmat
-ed4\ed4_skins\data\rvmats\glass_ca.paa
-ed4\ed4_skins\data\rvmats\lightbarredwhite.rvmat
-ed4\ed4_skins\data\rvmats\lightbarredred.rvmat
-ed4\ed4_vehicles\civilian\cars\bugatti_veyron\textures\interior_lod0.paa
-ed4\ed4_skins\data\textures\carbonfiber.paa
ed4\ed4_vehicles\civilian\cars\bugatti_veyron\textures\nodamage.paa
ed4\ed4_skins\data\textures\grille1.paa
ed4\ed4_vehicles\civilian\cars\bugatti_veyron\textures\lights.paa
ed4\ed4_skins\data\textures\undercarriage.paa
ed4\ed4_vehicles\civilian\cars\bugatti_veyron\textures\wheel.paa
ed4\ed4_skins\data\textures\tirea0.paa
ed4\ed4_skins\data\rvmats\glass_ca.paa
ed4\ed4_vehicles\civilian\cars\bugatti_veyron\textures\interior_lod0.paa
ed4\ed4_skins\data\textures\carbonfiber.paa
ed4\ed4_skins\data\rvmats\chrome.rvmat
ed4\ed4_skins\data\rvmats\glass.rvmat
ed4\ed4_skins\data\rvmats\skin.rvmat
ed4\ed4_skins\data\rvmats\lightbarredwhite.rvmat
ed4\ed4_skins\data\rvmats\lightbarredred.rvmat

EDIT:

After clearing "C:\Users\Jordan\AppData\Local\Temp\ARMAaddons" folder and deleting the proxies in my model, and rebinarizing, the p3d is included.

If I clear the above folder again and binarize the exact same way as before, the p3d is not included until the process is repeated.

Edited by eagledude4

Share this post


Link to post
Share on other sites

I would try reinstalling just binpbo and binarize tools. I had an issue when binarizing it would include my islands names.hpp file in the main config but they would appear in game. Reinstalling fixed the issue. Maybe it will for you too

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×