XeNTaX

ersel54 wrote:on forgeX beta/data location I think found something there is no ACR_MDL.stc file in that folder but there is ACB_MDL.stc and AC2_MDL.stc files.
can you take a look at setup?

The .stc files are simply text files that provide information on the various file formats. They have bearing what so ever on the function of the program.

If my previous suggestion does not solve your import issue, please provide with specific model names so that I may also test those models.

Thank you for your support,

MichaelDarkAngel wrote:

ersel54 wrote:on forgeX beta/data location I think found something there is no ACR_MDL.stc file in that folder but there is ACB_MDL.stc and AC2_MDL.stc files.
can you take a look at setup?

The .stc files are simply text files that provide information on the various file formats. They have bearing what so ever on the function of the program.

If my previous suggestion does not solve your import issue, please provide with specific model names so that I may also test those models.

Thank you for your support,

yes I tried what you said before but noway still error with viewing models and no uv maps when I export as .OBJ.
the model name is:
dataPC/_CC_G_fedayin_trainee_female/models/CC_G_fedayin_female_rank01_LOD0

I have no idea what the problem with your setup is that would be causing the import issue, or even the model viewing issue for that fact. You can open any of the exported OBJ files with notepad and clearly see the texture coordinates are there.
The second section where the lines start with vt are the uv map (texture) coordinates. Why they don't work for you and why the model viewer does not work... Sorry, but I am out of suggestions.

@MichaelDarkAngel: thank you for the answers. but, I've checked all the codes yes the codes are there but... I don't know why the uv maps are not there on max 2010? .
I hope that you can found the solution.

There is one more suggestion I can make. It may solve the model viewer issue, I doubt it would have any effect on the import issue. It may not work for either one, but it's the last thing I can think of.

Try updating your DirectX.

I can't open it, it stopped working, why???

thaitam7 wrote:I can't open it, it stopped working, why???

You probably tried to run it in a x64 operating system.
Same problem here, and no solution soon, then, try a v-machine or
get some x86 OS.

thaitam7 wrote:I can't open it, it stopped working, why???

It could be any number of reasons, without more specific information any answer would just be a guess.

Hi Michael!

With so much to read in this thread, it's unclear what state the beta is currently in. I'm hoping you can help me out since ForgeX stops working immediately when I try to run it. I'm running a 64-bit system and I have Revelations installed through Steam. From what I've read, it sounds like both of these things will prevent ForgeX from working. Do you have any suggestions? Or am I just out of luck for now? I'm trying to get the dlc Gladiator model for a mod project.

Best regards,
dragbody

I may have an idea about the uv maps / model display failure...

In some other cases i had problems with importing models cause the script / plugin used a different decimal seperator -> fucking up the coordinates

So what you can try: What is the decimal seperator in your country? "." or "," ?

Try changing it in the windows language settings from "." to "," or vice versa...

See if that helps

dragbody wrote:Hi Michael!

With so much to read in this thread, it's unclear what state the beta is currently in. I'm hoping you can help me out since ForgeX stops working immediately when I try to run it. I'm running a 64-bit system and I have Revelations installed through Steam. From what I've read, it sounds like both of these things will prevent ForgeX from working. Do you have any suggestions? Or am I just out of luck for now? I'm trying to get the dlc Gladiator model for a mod project.

Best regards,
dragbody

Sorry, I still don't own a 64-bit OS, so there is still no support for a version working directly under that OS. Best solution at this time is to try Marky's suggestion from this post.

Itze wrote:I may have an idea about the uv maps / model display failure...

In some other cases i had problems with importing models cause the script / plugin used a different decimal seperator -> fucking up the coordinates

So what you can try: What is the decimal seperator in your country? "." or "," ?

Try changing it in the windows language settings from "." to "," or vice versa...

See if that helps

I always forget about the decimal separator difference. Thanks for the tip

I found the solution for the uv maps / model display failure.
The problem is the one discovered by Itze, changing every "," in the .obj with a "." (using notepad), when you try to load the modified .obj, It'll have UV maps.

Could someone please get me 3D files of Iraqi city from Splinter Cell Conviction instead of me getting the game for that purpose? I mean that is Ubisoft game so it should work.

LaBamba wrote:Could someone please get me 3D files of Iraqi city from Splinter Cell Conviction instead of me getting the game for that purpose? I mean that is Ubisoft game so it should work.

No help here. Splinter Cell Conviction does not use Forge files. The files used by the game are completely different.

Hi all

I've read the previous messages but I didn't find anything about this issue. Opening both models from Brotherhood and Revelations, almost every model it's showed in the model viewer without textures:





Does it depends because they're static models? Also exporting in .obj format importing in 3ds Max 2009 and 2012 they're without textures or materials. Usually they're under the same material even when it's clear that the model uses different texture files. I'm using the same import settings posted here.

Those are the settings I'm using on Max 2012:



When it's easy discover some of the textures used by the model I can assign them in the mat editor, but usually the same texture it's assigned to every mesh, that creates wrong texturing:



The UV coordinates are wrong in Max 2009 (they look too small to fit the correct texture map), but it seems that in Max 2012 they're right. Maybe it could be a good idea edit the obj exporter to make it export ALSO all the linked texture files, indipendently if they're already extracted.

Any suggestions?