Author Topic: Oblivion problems involving meshes/textures.  (Read 1694 times)

After installing Millstone Farm I completed the quest and went over to it.


I got a mixing bowl of yellow triangles with "!" in them, AKA, error. I don't know what went wrong and I forgot how to properly install the meshes. I need a little help please.
I'm using Windows XP if that means anything.

Really, it loving REFUSES to work.
« Last Edit: June 12, 2010, 07:06:35 PM by Jacob/Lee »

with fallout 3 when stuff happened like that, you'd need an archive invalidator.

Missing models, Also that mod looks cool.

Oblivion is just awful with bugs like that.

Re-install oblivion. Seeing as bethseda refuses any support for the game.

Oblivion is just awful with bugs like that.

No.

Installing a mod incorrectly is not Oblivion's fault.

No.

Installing a mod incorrectly is not Oblivion's fault.
Thing is, oblivion is so stufftily made (great game though), that whenever you install a mod this has a chance of happening. This includes your x-box 360, with ONLY official mods like shivering isles.

Thing is, oblivion is so stufftily made (great game though), that whenever you install a mod this has a chance of happening. This includes your x-box 360, with ONLY official mods like shivering isles.

I've never had one error/missing texture/missing mesh/corrupt save/re-install/broken quest. So maybe you just suck at installing mods?

I've never had one error/missing texture/missing mesh/corrupt save/re-install/broken quest. So maybe you just suck at installing mods?
i dont play oblivion a lot enough to get mods
but that never happened to me in fallout 3

Thing is, oblivion is so stufftily made (great game though), that whenever you install a mod this has a chance of happening. This includes your x-box 360, with ONLY official mods like shivering isles.

I agree. Or the mods just don't sit right with the game itself.

In any case, game and all official addons for 9 bucks on Steam. I bought it! They come installed with the game, so it should all be working correctly.

But I've been wrong before.