The value of ESP was not properly saved across a
function call. This is usually a result of calling
a function declared with one calling convention
with a function pointer declared with a different
calling convention.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2001-06-10
assigned_to: nobody --> beosil
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2001-06-10
Logged In: YES
user_id=74825
As I have no access to MAX R4 (and won't have in the near
future), I am not able to help you much with this problem
at the moment. Have you tried debugging it? Compile the
exporter plugin as debug version and take a look where it
crashes. Does the skeleton and animation export work?
Another thing is that the exporter (v.0.1) is not very
stable itself. Make sure you have a mesh selected before
exporting, or it will fail and crash the whole application.
I am currently rewriting the whole exporter plugin to make
it user-friendly, stable and complete. I suggest we should
take a closer look at this new release and MAX R4 when I
have it ready. Ok?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2001-08-05
Logged In: YES
user_id=74825
The new exporter should work with max4. Test it out =)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2001-08-05
status: open --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
Error message :
The value of ESP was not properly saved across a
function call. This is usually a result of calling
a function declared with one calling convention
with a function pointer declared with a different
calling convention.
Logged In: YES
user_id=74825
As I have no access to MAX R4 (and won't have in the near
future), I am not able to help you much with this problem
at the moment. Have you tried debugging it? Compile the
exporter plugin as debug version and take a look where it
crashes. Does the skeleton and animation export work?
Another thing is that the exporter (v.0.1) is not very
stable itself. Make sure you have a mesh selected before
exporting, or it will fail and crash the whole application.
I am currently rewriting the whole exporter plugin to make
it user-friendly, stable and complete. I suggest we should
take a closer look at this new release and MAX R4 when I
have it ready. Ok?
Logged In: YES
user_id=74825
The new exporter should work with max4. Test it out =)