Jump to content
Sign in to follow this  
[frl]myke

Weird Proxy displacement problem

Recommended Posts

Ok, i've ran into this and i'm out of ideas. Let first see if i get the basics right in my mind:

A proxy in O2 will place the relevant model (in this case a bomb) according to the proxy position. Reference point at the proxy triangle is the 45degree corner (can't describe it better, i hope you get the point). This triangle point is where the [0,0,0] MLOD coordinate of the attached MLOD will be placed. If the visible model is not centered to absolute 0, it will be shown on the first object with this offset.

Ok, knowing (guessing) this, if i displace any missile or bomb MLOD downwards in the MLOD so that not visual model is centered but it's upper edge is on zero line and on the plane i put the proxy accordingly, any bomb/missile which is offcentered the same way should always fit perfectly to the weapon holder.

Got some pics to make it better understandable:

First, planes weaponholder and 3 proxies:

372-proxies.jpg

As you see, the proxies fit exactly with the weaponholder.

Now to the bombs itself, first the gbu12:

372-gbu12.jpg

Note that it is offcentered downwards.

Now the Mk82:

372-mk82.jpg

You see, the Mk82 is the same way offcentered as the GBU12. Also general measurements are almost identical, ignoring that the GBU12 is longer but here this doesn't matter.

Please note that the proxies on the plane are neither GBU12 nor Mk82 but AGM65 so i can exclude this as the source of the issue.

Lets now see how it looks ingame. Note that both planes are the same p3d, only difference is the magazines and weapons loadout defined in the config:

First the GBU12:

372-gbu12_ingame.jpg

Fits perfectly, exactly what i've expected to see.

Let's now look at the Mk82:

372-mk82_ingame.jpg

As you see, the bombs are burried into the weapon holder.

First idea was a missing config entry so i've added this:

class CfgNonAIVehicles {
class ProxyWeapon;
class Proxyproxy_holder: ProxyWeapon {
	model = "\glt_f16\nwep\proxy_holder.p3d";
	simulation = "maverickweapon";
};
class ProxyGLT_AGM65: ProxyWeapon {
	model = "\glt_f16\nwep\GLT_AGM65.p3d";
	simulation = "maverickweapon";
};
class ProxyGLT_AIM9: ProxyWeapon {
	model = "\glt_f16\nwep\GLT_AIM9.p3d";
	simulation = "maverickweapon";
};
class ProxyGLT_AIM120: ProxyWeapon {
	model = "\glt_f16\nwep\GLT_AIM120.p3d";
	simulation = "maverickweapon";
};
class ProxyGLT_gbu12: ProxyWeapon {
	model = "\glt_f16\nwep\GLT_gbu12.p3d";
	simulation = "maverickweapon";
};
class ProxyGLT_mk82: ProxyWeapon {
	model = "\glt_f16\nwep\GLT_mk82.p3d";
	simulation = "maverickweapon";
};
};

But this didn't had any influence at all.

Also checked multiple times if maybe path to p3d could be wrong but there i can definately say, everything is ok.

class GLT_Mk82_Bo: Bo_GBU12_LGB {
	model = "\glt_f16\nwep\GLT_mk82.p3d";
	proxyShape = "\glt_f16\nwep\GLT_mk82.p3d";
	canLock = 0;
};

So i'm kinda out of ideas, any help is more than welcome.

Share this post


Link to post
Share on other sites

you might wanan check your bomb.p3d are in the right location I.E center of the O2 dialog.

Only other way to fix it is to move the Proxy on the aircraft and save it to a new p3d then defien that new model in the config and the MK82 version.

I might be wrong but this is how i fixed ArmAI stuff in the past

Share this post


Link to post
Share on other sites

Make sure the Mk82 has the named property "autoCenter" with the value 0 (I like to put this in the geometry lod and nowhere else)

Share this post


Link to post
Share on other sites

@DM

You, Sir, are a genius. That solved the problem in no-time. Thanks a lot, now life has a meaning again. :D

No honestly, this was giving me headache for hours. Completely forgot (or better said: don't know much about) named properties. A quick countercheck showed me that in the GBU12 this value was set already.

@armatech

Thanks for your input too, really appreciate it. But for some special reason it needs this off-centered concept. This will be part of another little project for which i want this plane and weapons be ready for.

:EDITH:

AARGH....as soon one thing works, another gets broken. Now the missiles/bombs are showed correctly, no matter what combination i've put. Now another problem raised out of nowhere:

When firing a weapon /no matter which, affects all of them) the missile/bomb starts from planes center instead of the weaponholder. Also the model on the weaponholder isn't removed. It worked before, also with the GBU12 (which had the autocenter = 0; already applied. Any ideas on this?

Edited by [FRL]Myke

Share this post


Link to post
Share on other sites

To make it fire from set locations you need to add memory points

Left side

L Raketa

Right side

R Raketa

Share this post


Link to post
Share on other sites

Check if the models in the proxy definitions still match your models. May be you renamed your .p3d file and the proxy entries in the f-16. In A1, the maveric proxies must be named AGM114Hellfire, even when using an alternative weapon layout, else the proxies in the model become static proxies and will be launched from those entries armatech mentioned.

Edited by modEmMaik

Share this post


Link to post
Share on other sites
Check if the models in the proxy definitions still match your models. May be you renamed your .p3d file and the proxy entries

Yep, that was the solution for me when my B52 bombs started spawning at model center.

Share this post


Link to post
Share on other sites

@armatech

this goes for FFAR style rocketlauncher but not for proxy weapons like AGM65 or sidewinders. Check the BIS Sample Models, they have the memory points at the place where the FFAR pods are. At the proxy places there aren't any memory points.

@modeEmMaik & [APS]Gnat

Ok, i've completey redone the proxies now (Create>proxy) and made sure i've choosed the correct .p3d but this didn't solved the problem. Last thing i'll try right now is to switch all proxies to original BIS proxies. Maybe it dislikes the custom rocket models.

I'll report back if this helped.

:EDITH:

Problem solved. I've replaced all custom missile proxies with BIS AIM9xSidewinder and now it works flawless. I'm now just curious whats the difference between those.

Edited by [FRL]Myke

Share this post


Link to post
Share on other sites

:EDITH:

Problem solved. I've replaced all custom missile proxies with BIS AIM9xSidewinder and now it works flawless. I'm now just curious whats the difference between those.

Sounds like the proxy wasn't defined correctly in the config.cpp

Share this post


Link to post
Share on other sites

Can you be more descriptive please? Or maybe an example hot it should have be done? It's obvious thats something wasn't done properly, i already knew that.

Share this post


Link to post
Share on other sites

I'm a bit lazy when it comes to proxies, so I've tended to go your rout.

CAVEAT: My ArmA2 copy is still in transit from the UK to little ol' NZ... so I am not sure how different proxy implementation is, but I suspect it will be more or less along the same lines as ArmA.

For the B1B i defined the proxies as follows:

Make sure the model is defined correctly in the Ammo config section:

class CfgAmmo {

...

class Bo_GBU31_LGB : Bo_GBU12_LGB {

model = "\usec_b1b\GBU31\GBU31.p3d";

proxyShape = "\usec_b1b\GBU31\GBU31.p3d";

hit = 20000;

indirectHit = 5000;

indirectHitRange = 100;

laserLock = true;

canLock = LockYes;

};

...

};

And then, importantly, make sure it is defined in the section for proxies as follows:

class CfgNonAIVehicles {

class ProxyWeapon; // External class reference

class Proxygbu31 : ProxyWeapon {

model = "\usec_b1b\GBU31\gbu31.p3d";

simulation = "maverickweapon";

};

...

};

From what I can guess, the engine needs to know that the proxy object is for special simulation use. Therefore, you define here how the proxy is used.

Hope that helps.

Share this post


Link to post
Share on other sites

@Rocket

Check my startpost, this is exactly what i had. So sadly no, this doesn't help unless you can see something is wrong there. But thanks anyway, any input always welcome.

Share this post


Link to post
Share on other sites
@Rocket

Check my startpost, this is exactly what i had. So sadly no, this doesn't help unless you can see something is wrong there. But thanks anyway, any input always welcome.

Ah I see, have you made sure the proxy is created in all LODs (not just the main resolution LOD). I believe it has to be in the Fire Geometry and Geometry LOD.

Share this post


Link to post
Share on other sites

Ah, i think we get it there. They weren't in the geometry LOD. I'll try this and will report back. Thanks for the infos, much appreciated.

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  

×