Scolring - Forum

Alors là, même si avec ma modif ça marche pas, je pige pas.
La fonction ScolLoadPlugin est déclarée exactement de la même manière que dans les autres dll, à savoir:

extern "C" __declspec (dllexport) int ScolLoadPlugin(mmachine m, cbmachine w)

Donc c'est bizarre que juste pour celle-ci, ça ne fonctionne pas. Iri, je ne sais plus si on l'avait déjà fait, mais que donne Dependency Walker (http://www.dependencywalker.com/) sur la dll security, sous wine?
Normalement, il devrait afficher les deux fonctions exportées (ScolLoadPlugin, ScolUnloadPlugin) en clair, cad avec un "C" dans la colonne "E" (et pas de caractères bizarre genre "@^$!" dans le nom).
Il y a-t-il des module non chargés dans la liste du dessous (dependences de security.dll non trouvées)?

L'origine a en fait été trouvée, mais je vois pas encore comment corriger...

Another thing that you must check when creating materials that uses textures with blender is that you use the "UV coordinate" mapping (in "textures" panel, "mapping" subpanel"), not the default "generated" one, otherwise it will not work. That's how Ogre works with blender, it's a bit of supplementary work because you will need to "unwrap" your model in the uv editor.

Hello,
You said that you use "Ogre Meshes Exporter", which is the script for blender version up to 2.49. If you use Blender 2.5+ (or 2.6+), then you mustn't use this exporter! Use Blender2Ogre instead:
http://www.ogre3d.org/forums/viewtopic.php?f=4&t=61485
http://code.google.com/p/blender2ogre/

Then, to use OgreXMLConverter automatically, you'll need to extract Ogre's tools to a directory and:
* If you use "Ogre Meshes Exporter" for blender 2.49, then clic on the "preference" button in the configure panel of the exporter

And enter the path to the directory where you extracted ogre's tools.

* If you use Blender2Ogre, then configure the OgreXMLConverter path in the "OGRETOOLS_XML_CONVERTER" field:

You can also convert .mesh.xml file to .mesh files by dragging the xml file on the OgreXMLConverter icon (but it's a pain to do it recursively). Notice that a .mesh can be converted to a .mesh.xml by dragging the .mesh file on OgreXMLConverter (can be useful sometimes for some mesh debugging purpose).

It may usefulness to you, but i re-post the links of 2 blender export tutorial videos we made some time ago:
http://www.youtube.com/watch?v=jY2sauVo4CA (for blender up to version 2.49)
http://www.youtube.com/watch?v=hhoFkwiDwO8 (for blender up to version 2.5+/2.6+)

Does your problem is purely related to the mesh that does not appears on the ATI pc (you may need a special technique on your material to handle radeon rendering, it happens sometimes with those graphic cards), I mean, did you try to render a test scene on the ati computer without the ar stuff?

Il faut vraiment que je prenne 5 minutes pour regarder ça...

On precision: if you want to use it, then download the "nightly builds", not the alpha version which is really outdated.
But, the problem with those nightly builds is that it may work or not from one day to another... Fortunately, the developers are really responsive, and if you have a problem, you can use theirs forum. Myself I had a request about MakeHuman, and they coded my proposal within days .
But the export from makehuman to blender (and from blender to ogre3d) is not as easy as it sounds .

It seem nice, but the problem is that the licence is GPL: in two words, you can't use it in a commercial application.
As OpenSpace3d have an LGPL licence (notice the "L" as in "Lesser", less restrictive), we do not restrain our user to a non-commercial use... Scol have another licence, a bsd like licence, which does not restrain commercial usage neither.
BUT i'm not saying that it's not legit to do a scol plugin (and the corresponding openspace3d plugit) with this library, just that we cannot distribute it under the same conditions as OpenSpace3d: so we will keep the actual solution, as we have the right to distribute it in the core package. An additional plugin is doable, but the LGPL licence mention must be explicit, and the impossibility to use it for commercial usage too.
Everything is complicated when it comes to legal issues

Let me know if you need some help, one of the aspect of this conversion is to get rid of the "scol sdk" include files (not the scol_sdk directory, i'm talking about the scol sdk setup with 3 ugly includes files in it), and using the file from the vm. This way we are sure that the structures/defines shared along the plugins and the vm are consistent (the "scol sdk" includes is actually made from peace of code extracted from multiple vm include files, that's not "clean").

Thanks Bob, I already renamed it anyway .