Jump to content
  • 0

Okay, what the hell?


Malqua
 Share

Question

Okay, so, I'm having trouble with a map I'm trying to import. It imports seemingly fine, except for the water texture, which gets replaced in the MTL and Texture File by a rock texture that doesn't exist (and even when imported there is no image, so I don't even...).

 

 

  Reveal hidden contents

 

 

Okay, so there's the texture issue, BUT I also get a weird error (that I've never experienced before) where I get close to certain spots on the map and it will freeze.

 

 

  Reveal hidden contents

 

 

So, yeah. Can anyone help me with this?

Link to comment
Share on other sites

20 answers to this question

Recommended Posts

  • 0

Now spinout's converter is freezing on Nemu? o.o If it's doing that, you're probably screwed, it only did that on PJ64 for me, but Nemu always worked fine. I would try a different version of the converter; which one are you using now?

 

EDIT: Also, I noticed a bunch of stuff in your first spoiler tag. You appear to have a problem with the way you've triangulated your map; I think you have a few quadrilaterals here and there, and you have a LOT of unnecessary faces from what I can tell. Since you appear to have Pro, you can just triangulate the map upon exporting it as an obj, so don't do triangulation manually--that's more likely to cause problems. Anyway, quadrilaterals or 4+ sided polygons would explain your missing faces, unless they have collision there--I never had missing mesh geometry except with spinout's old converter. If that's the case, I'm not sure what the problem is, but it's definitely worth a shot to get a triangulation plugin for SketchUp and try exporting this again. If you can't find one, let me know and I'll send it your way.

Link to comment
Share on other sites

  • 0

Regarding the crash error, can you try this with a version of the converter that uses collision_fixer.exe?

I never had any crashes when spinout's converter relied on it but I've heard multiple times of people having problems with the newer versions that don't rely on it and I've had the same problem when using the SM64 to Zelda64 converter too.

Link to comment
Share on other sites

  • 0

What Naxylldritt said: good, read it. As for water, I recommended using an actor for a transparent water texture, you will find that you have much better luck with it. Quoting the actor list by variables:

0065:0059:1804:Large Square of Water

0065:0059:1A02:Large Square of Water

0065:0059:3203:Large Square of Water

0065:0059:FF00:Large Square of Water

 

  On 1/7/2011 at 4:21 PM, 'DeathBasket' said:

Regarding the crash error, can you try this with a version of the converter that uses collision_fixer.exe?

I never had any crashes when spinout's converter relied on it but I've heard multiple times of people having problems with the newer versions that don't rely on it and I've had the same problem when using the SM64 to Zelda64 converter too.

 

Are you using a version of SM64toZ64 with collision_fixer.exe ? The newest versions have it built in and should work flawlessly.
Link to comment
Share on other sites

  • 0
  On 1/8/2011 at 8:29 PM, 'DeathBasket' said:

I used one of the versions where it's built in. It could be an emulation error on PJ64's behalf since it seems to work fine in Nemu.

 

If that is the case, it's probably an off-by-one error, but I don't know tbh
Link to comment
Share on other sites

  • 0
  On 1/22/2011 at 7:45 PM, 'ZethN64' said:

Yeah I've experienced this problem before as well, I thought it was a bit odd that it was freezing like that. Also Nemu ignores most errors and plays anyways so cause it runs in Nemu doesn't mean its working correctly.

 

Then again, just because it crashes in PJ64 does not mean there is something wrong with it. It's an infinite problem caused by the inaccuracies in emulation.
Link to comment
Share on other sites

  • 0

I think he means more that it's impossible to determine if the error is caused by faulty emulation in PJ64, or if Nemu is simply ignoring errors that PJ64 stops for. Which is a good point--unless something like this is actually tested on an N64, it's impossible to tell what the problem might really be.

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.