Need help with proxy paths

[[GLT] Legislator 66]

Hi guys,

I need your help again. I'm currently stuck with something that seems to be a proxy path thing. I tried to port the A2 hunting rifle with the help of the sample models to A3. In buldozer everything in the preview is fine without errors. I also applied a new path to the muzzle proxy: http://minus.com/i/b2F5MnIuZ37Wk

However ingame when I add the new weapon to the player, I get a pop up error message.

Warning Message: Cannot open object ca\weapons\zasleh2_proxy.p3d

Warning Message: Cannot open object ca\weapons\zasleh2_pilot_proxy.p3d

Here's my model.cfg

class CfgModels {
class Rifle_Base_F;
class GLT_Huntingrifle : Rifle_Base_F {

 	class MuzzleFlashROT {
			selection="zasleh"; 
	};
};
};

I have a similar issue after porting over the C130J wreck.

Can someone please help to get this fixed?

[teacup 2]

Tinkering with the model.cfg won't do the trick here, you have to go into the model, and swap proxy paths. Either you point the proxies to their ArmA3 equivalents, or copy over the ArmA2 proxies into your addon and refer to them.

[[GLT] Legislator 66]

Hi there,

that's what I did. I took the original proxy model from A2 and moved into to my P:\ drive into my addon folder. Then I opened the hunting rifle p3d and changed the proxy path: http://minus.com/i/b2F5MnIuZ37Wk

But it is still not working :( If there is still a reference to the old arma 2 path, I can't find it.

[teacup 2]

Did you do it in all the LODS? To make sure there's no reference to the old proxy paths, open the P3D in a hex- or even text-editor and search for "proxy:". You will find all proxies and ensure you didn't miss some.

[[GLT] Legislator 66]

Ok didn't know that. It's still not working though :(

Here's what I did:

- I opened the p3d file in the windows text editor

- indeed I found references to ca\weapons\zasleh2_proxy.p3d and ca\weapons\zasleh2_pilot_proxy.p3d

- I corrected them to glt_weapons\huntingrifle\data\zasleh2_pilot_proxy.p3d and glt_weapons\huntingrifle\data\zasleh2_proxy.p3d and saved the file

- now I can't open the p3d file in oxygen 2 anymore, it crashed (don't worry, I got a backup file ;) )

- I binarized everything and took a look in arma 3 how the addon might work now. I'm still getting the pop up error

However I'm wondering. If those old paths were still present, did oxygen2 not apply the new path or did I miss a setting, button or menu where I have to check them?

Anyway, I'm going to undo my changes and try to open everything in a hex editor next. I hope this isn't against the EULA.

[da12thMonkey 1943]

Legislator;2728219']

Here's what I did:

- I opened the p3d file in the windows text editor

...

Don't do that. That's how you're corrupting the .p3d

You have to open the model in O2' date=' right-click all the selections called [b']proxy:ca\weapons\zasleh2_proxy.p3d[/b] in the list of named selections, select 'Rename' from the drop-down list that appears and and change the path here. Then you have to repeat this process for every LOD that contains the proxy you want to replace.

Hex editing only works if you use the EXACT same number of characters for your path as were in that path in the .p3d to begin with, but I'm not even sure you can hex edit proxy paths to begin with (never tried it - I only know that it can work for textures)

Edited July 12, 2014 by da12thMonkey

[[GLT] Legislator 66]

Dear Sirs, the mystery is solved :) I think I deserve a huge facepalm. I never tried to doubleclick the several LODs. Then I did see more proxies of which I had to change the paths :D Thanks to both of you, everything is working now.