![]() |
Quote:
|
Quote:
|
Quote:
|
Quote:
[Only registered and activated users can see links. Click Here To Register...] |
Amazing work, Glandu, thank you so much!
I don't know if this is a problem on my part, but every single time I import an nx3, replace the model, then export straight away, the texures won't show up in game. However, saving the scene in blender and loading it again right before exporting seems to magically fix the problem. On a different note, Glandu, would it be possible to get textures to repeat mirrored instead of tiled? (the option in Textures/Image Mapping, Mirror: X and Y checked) |
Quote:
But anyway, here is the fixed file for exporting mesh without textures: [Only registered and activated users can see links. Click Here To Register...] But keep in mind that if your model file is the same as in test.rar you gave, it will only export the monster, not your plane, as you can't export object without bones along with object with bones. You mush set the armature (polymsh) as the parent. For that, drag the plane onto the polymsh armature: [Only registered and activated users can see links. Click Here To Register...] Then choose "With Empty Groups" to set no weight for bones (your plane will not move when bone will be moving): [Only registered and activated users can see links. Click Here To Register...] Then you should have this outline: [Only registered and activated users can see links. Click Here To Register...] And you can export your mesh. If your plane is not correctly exported, try to combine your plane with polymsh object: Select your plane, THEN select the polymsh_0 while pressing shift (to select both objects, the order plane then polymsh is important) Then press CTRL+J and your are done. Quote:
For texture, UV need to be between 0 and 1, so texture repetition is not possible. I might test that further later, but for now, repeat the texture manually and use the repeated texture for example, this feature is not a priority, before that having the possibility to import all possible nx3 files. For the exporter, there are also many cases that I have to handle, like a mesh without bones with another mesh which have bones (in nx3 files, the bones are for the whole file and all meshes must reference it it seems) |
Wow I have problemes
1-when import : [Only registered and activated users can see links. Click Here To Register...] 2-when Export : [Only registered and activated users can see links. Click Here To Register...] I hope you help me bro |
Quote:
As I can see, you didn't have blender in Program files(x86) so use the same DLL as your system architecture. As said before, the first error is not a problem, it does not prevent the plugin from working correctly. (I have this error too, it's related to msvc runtime dlls, manifests and winsxs, maybe because blender use it's own shipped version of msvcrXX.dll) |
thank you glandu
but I Put the DLL file in Blender.exe Folder [Only registered and activated users can see links. Click Here To Register...] And the same Prolem |
Are you sure you used the x86 version of the DLL ? If yes, use process monitor to see where blender try to load the DLL.
Also, try with blender version 2.64, it's the version I use to make the plugin (but I didn't noticed errors with blender 2.67, so that should not be the problem) |
I'am Sure glandu
I use x86 Version And I try To put x64 dll and the same error I search in Google but Nothing Help Me |
Then use process monitor [Only registered and activated users can see links. Click Here To Register...]
I can't help you more if you don't use that (or anything that can tell where Blender is searching for BTRFdom.dll). Else try to run blender.exe directly instead of a shortcut in the start menu or on the desktop to ensure that the blender's directory is it's current directory. (In fact I don't use shortcuts, maybe they are the cause but I don't think) In process monitor, filter the path to show lines containing "BTRFdom" so you will end up with all searched path. Then post that here. (Or it will be enough for you to figure out where to put the DLL.) Also, your case is very unlikely as you the import works and it find the DLL but not the export script although they use the exact same line of code. (But anyway, process monitor will tell what's wrong) |
SomeThing Like this ?
[Only registered and activated users can see links. Click Here To Register...] |
Yes, but with NAME NOT FOUND, as here it show that the DLL was correctly loaded (probably the importer which works but not the exporter as you explained before)
|
I try with 2.64 version but the same Problem Too
Do You have any Idea Bro ? |
| All times are GMT +1. The time now is 04:02. |
Powered by vBulletin®
Copyright ©2000 - 2026, Jelsoft Enterprises Ltd.
SEO by vBSEO ©2011, Crawlability, Inc.