OFP Forum, OFP Home, OFP File Formats, OFP Tools, OFP Missions, OFP 3D Modeling, OFP Terrain

Operation Flashpoint (OFP) aka ArmA: Cold War Assault (CWA)

There are several binarize errors on p3d models. For example Bad proxy object definition proxy:<something> This could mean the several things like:

1. There is a selection but no proxy present
2. there is selection and proxy but with more points or faces then 3 points/1 face
3. A proxy is also part of a componentXX in one of the logical lods

To fix these you need to check the model that with this proxy, there is actual selection present, for example. Hmm. Make a new selection for the proxy, then redefine the proxy to this selection.

When you binarize and muzzle flash is on, you need to make sure the config.cpp wont have #include “blabla.hpp” for cfgModels, it does not work. Put cfgmodels into the config.cpp file.

Shape p3d:geometryView - bad components. View Geometry, don’t put proxys there.

Shape p3d:geometry - bad components. There is otochavlen and otocvez? Remove them.

Shape <addon>\<p3d>:geometry - bad components

Shape <addon>\< p3d>:geometryView - bad components
Cause: what it says, bad components.
Fix: Delete old components, then Structure → Topology → Find Components.

FireGeometry, has cargo proxies in componentXX’s, if you remove these, bad components errors disappear. But it is the right thing to do, I don’t know!?

Strange convex component <addon>\<p3d> in Component01:geometryFire, it means propably a proxy. But is it right thing to remove? I don’t know ?

<addon>\<p3d>:8.82165: Bad proxy object definition proxy:bmpcommanderout.01, means the wrong proxy is in the lod 8.very long strange number.

<addon>\<p3d>: Proxy object should be single face proxy:jeepgunner.01, no idea

<addon><filename>.p3d:1200: Bad proxy object definition proxy:<name>.01
Cause: There is a selection but no proxy present, on LOD 12.
Fix: Add proxy.

Cause: There is selection and proxy but with more points or faces then 3 points/1 face
Fix: ?

Cause: A proxy is also part of a componentXX in one of the logical lods.
Fix: ?

Strange convex component <addon><filename>.p3d in Component01:geometry
Cause: ?
Fix: ?

Strange convex component <addon><filename>.p3d in Component13:geometryView
Cause: ? Fix: ?

Strange convex component <addon><filename>.p3d in Component13:geometryFire
Cause: ?
Fix: ?

Shape <addon><filename>.p3d:geometryView - bad components
Cause: ?
Fix: ?

No neighbourgh
Neighbourgh in other component
Component06
Cause: ?
Fix: ?

<addon><filename>.p3d: Unknown map type road
Cause: ?
Fix: ?

<addon><filename>.p3d: Unknown map type forest
Cause: ?
Fix: ?

<addon>\<p3d>: Proxy object should be single face proxy:jeepgunner.01
Cause: ?
Fix: ?

Problem: botched proxies
Error: <addon><filename>.p3d:1200: Bad proxy object definition proxy:<name>.01

Cause 1: There is a selection and a proxy but with more points or faces then 3 points/1 face
Fix: Make sure all proxy shapes consist of only 3 vertices and one face. (I've seen models where 6-vertice/2-face shapes are tried to be passed on as proxies…that's bad)

Cause 2: A proxy is also part of a componentXX in one of the logical lods.
Fix: This happens when proxies are both a selection named “ComponentXX” and “<name>.0x.”. Proxies have to be unique. In other words, if there's a selection “ComponentXX” consisting of the vertices and face of a proxy, that selection needs to be removed and only the “<name>.0x” selection should remain.
Background: When does this occur? It happens when you use an operation in O2 that enumerates the components of a certain LOD. Examples of such operations are the ones in the menu Structure→Topology (“Find Non-Closed” and “Find Components”) and in Structure→Convexity (“Find Non-Convexities” and “Find Component Convex Hull”). For example, Find Components will search for and enumerate all components in a certain LOD. The result is a list of selections named Component01, Component02,… and so on. The proxies in a LOD will also be listed in there. This is undesirable, since the proxies should only be in selections named “proxy:something.0x”. The solution is to remove all the selections named “ComponentXX” that are proxies.
Warning: One has to be careful when removing the excess “ComponentXX” selections containing the proxy objects. After the pruning, the list of components have to remain ordered and without gaps in the numbering. What often happens is that you'll see a Component0x that is a proxy and should therefore be deleted. The problem is that Component0x isn't the last in the list, but sits somewhere in the middle. Removing that will get you a gap in the numbering. So how do we make sure that any proxies get listed at the end of the component list? The solution is to make the proxies' vertices the last ones in O2:s list of vertices. Do that by cutting out the proxy shapes and then pasting them back again. After doing that, repeat the “enumerative operation” you did (eg “Find Components”). When all the proxies are listed last among the components, you can safely delete the offending last “ComponentXX”:es that correspond to the proxies. Problem solved.

Problem: strange convex components
Error: Strange convex component <addon><filename>.p3d in Component01:geometry
Error: Strange convex component <addon><filename>.p3d in Component13:geometryView
Error: Strange convex component <addon><filename>.p3d in Component13:geometryFire
Error: Shape <addon><filename>.p3d:geometryView - bad components

Cause: All of these can be caused by faulty and/or missing proxies. They can also pop up for other reasons, none of which I'm too familiar with.
Fix: Begin with unscrewing your proxies in all LOD:s and see if that helps.

Our binarize errors PMC Tactical forum topic.