[Mongoose]

I know that the problem of the Maxim not working with recent builds/VP files is well-known, but I've never found a clear way to resolve it.  I've heard that temporarily removing one of the VP files (aseffects, maybe?) fixes it.  Is this the only way to fix it, or could some permanent solution be found that doesn't involve tinkering with the VPs?  It gets to be annoying when you go with the default loadout in a mission and find out that it includes a Maxim, especially when the Maxim would be a huge help.  The most annoying mission of all was the FS2 main campaign mission "The Fog of War," where the Maxim is the only primary you have by default; taking out those gas miners with just secondaries and your wingmen took a while.

[Descenter]

I've also ran into problems running that particular missison, in where it just booted me to Windows without any errors.  However,i have come to the conclusion that the problem is in the textures.vp and the zpack.vp, and had to totally move the .VP elsewhere to get past the mission.

[WMCoolmon]

http://www.hard-light.net/forums/index.php/topic,29938.0.html

[karajorma]

The problem is occuring because the ships.tbl in the mv_aseffects.vp does not have the settings required for ballistic primaries.
 The ships.tbl in mv_effects folder however does. Extracting this and placing it somewhere higher priority will allow the Maxim to work with the main campaign.

It will not  fix any problems you may have had with mods that use their own ships table but don't use their own weapons.tbl. The only cure for that is to manually fix their tables or get rid of mv_aseffects.vp when you play them.

[Mongoose]

Thanks for the help.  Will this discrepancy be fixed in the next version of the VPs, or are the different ballistic settings necessary for something else?

[karajorma]

Almost certainly it was an oversight which will be fixed in later releases. The changes to the ships.tbl have no effect unless you're using ballistic primaries like the new maxim.