As the title says my BO2 perks are being weird but as you can see in the background the other perks work fine



anyone know of a way to fix this?

The FX were never set up in Bams scripts and your using those right?

or if you mean tombstone, did you set the model on textures to unlit?

The FX were never set up in Bams scripts and your using those right?

or if you mean tombstone, did you set the model on textures to unlit?

im using bams scripts but these are models i have exported from BO2 and then exported to xmodel_exports in maya so the scripts are bams but the models not

right, but when you converted the models, you need to select the textures that glow and make them "model unlit" so they glow

unlit means its always lit, not effected by map lighting i believe

So on tombstone, whatever texture you have on the sign at the top and the texture behind the vents should be unlit, the rest (so the texture that covers the rest of the machine) should be normal

If its set up right when you view it in assman, double check its actually swapping the model to the on model

right, but when you converted the models, you need to select the textures that glow and make them "model unlit" so they glow

unlit means its always lit, not effected by map lighting i believe

So on tombstone, whatever texture you have on the sign at the top and the texture behind the vents should be unlit, the rest (so the texture that covers the rest of the machine) should be normal

If its set up right when you view it in assman, double check its actually swapping the model to the on model

the crazy part is i have them all (all the _on materials in assman) as unlit (well model_unlit) including the BO 1 perks and as you can see in the background of the image they work fine but cherry, whos who and tombstone refuse to work

cherry im pretty sure doesnt actually use unlit textures, whole model is 2 meshes and one of those is the zombie head inside the machine

its just a well placed light that makes it look lit

If its literally just that model, triple check it has swapped to the on model with iprints, last time i had this issue i had a typo so it didnt swap. Still worked but the model didnt swap