Star Wars - The Old Republic - Beta - GR2 model

[mvanderw]

link not working
anyone have a new link ???
thx

Since it's such a cool tool I'll put it up until Dionix187 sees this.

http://holocron.so/files/tormyp.tar.bz2

[Privateer]

The contents of this post was deleted because of possible forum rules violation.

[mazor]

How do you use the .gr2 converter to .obj tool, it does nothing but quickly bring up the cmd window? I tried running it to convert the gr2 model found in this thread and nothing is exported.

[Privateer]

Do a drag and drop.
Just drag the GR2 file you want exported onto the program.

Or you can try this one
http://www.mediafire.com/?2hd9vje40v2z2fd

[Privateer]

Something you might also want to keep in mind.
The Granny Sytem allows modifications as the Devs see fit to code them.
An Exporter for one Games GR2 files may not work for other Games GR2 files.
It's a very modifiable system if the Devs aren't confused by it all.

[CZW]

The contents of this post was deleted because of possible forum rules violation.

[Privateer]

PM sent.

[CZW]

Privateer, pm receive ...

same problem ...
i use Deep exploration to open it ..
screen on the brigde

[Privateer]

OK. I missed that section.
I saw something else that looked weird.

Anyone have the textures for this Unit?
I'd like to see it textured but I'll look at the GR2 data itself and compare to exported information.
Does anyone have an 'in Game' shot also?

In many Games? Somethings look all screwed up on exporting but how the Engine uses the Meshes explains alot of why things appear screwed.
As an example, You can find the Open Bunker I did for SH5.
You'll see many mistakes in the Sub Bunker but you were never supposed to be able to go there!
I edited the GR2 file and now you can.

[CZW]

The contents of this post was deleted because of possible forum rules violation.

[Hairless Wookiee]

It's the low LOD model for long distance stuff. Chances are the errors could exist in the original model, as often times game devs will generate lower LODs automatically through something like Optimize, or much more likely a specialist poly reduction plugin/script. Those sorts of operations tend to result in all sorts of mesh errors, particularly if the reduction is aggressive. Usually in-game it's a non-issue, as you can't see it from the distances the game uses the model at.

[CZW]

It's the low LOD model for long distance stuff. Chances are the errors could exist in the original model, as often times game devs will generate lower LODs automatically through something like Optimize, or much more likely a specialist poly reduction plugin/script. Those sorts of operations tend to result in all sorts of mesh errors, particularly if the reduction is aggressive. Usually in-game it's a non-issue, as you can't see it from the distances the game uses the model at.

the hashlist is partial at this time, yes ..
the name refered to the LOD, ok, but the model is fully fonctionnal
but into this model, you have the model and the LOD inside
here it's present the model, not the LOD
the LOD01 in any case, is the model very close ...

wait and see the specialist ^^

[Hairless Wookiee]

For veh_imp_capital_destroyer I am seeing veh_imp_capital_destroyer_lod02 and veh_imp_capital_destroyer_lod03, so presumably LOD01 is just the first LOD graduation and thus still contains a fairly reasonable amount of detail.

Speaking of the Imp Destroyer, I noticed that processing the Voidstar variant of the model (veh_imp_capital_destroyer_voidstar) with Privateer's app results in the following message for all textures in the MTL files:

No Materials, Invisible part, or texture Name located in Extended Data Block.
Extended Data Block access Code in progress.

It looks to be just the base destroyer meshes with an additional set of bridge meshes to make it look unique, but presumably they did something different with the structure of that particular file. Judging by the message, this will need to wait for an update of the app.

[CZW]

For veh_imp_capital_destroyer I am seeing veh_imp_capital_destroyer_lod02 and veh_imp_capital_destroyer_lod03, so presumably LOD01 is just the first LOD graduation and thus still contains a fairly reasonable amount of detail.

Speaking of the Imp Destroyer, I noticed that processing the Voidstar variant of the model (veh_imp_capital_destroyer_voidstar) with Privateer's app results in the following message for all textures in the MTL files:

No Materials, Invisible part, or texture Name located in Extended Data Block.
Extended Data Block access Code in progress.

It looks to be just the base destroyer meshes with an additional set of bridge meshes to make it look unique, but presumably they did something different with the structure of that particular file. Judging by the message, this will need to wait for an update of the app.

i haven't find it ...
share a pack ..
i see only one scare in character selection folder, it seems a background picture

[Privateer]

Speaking of the Imp Destroyer, I noticed that processing the Voidstar variant of the model (veh_imp_capital_destroyer_voidstar) with Privateer's app results in the following message for all textures in the MTL files:

No Materials, Invisible part, or texture Name located in Extended Data Block.
Extended Data Block access Code in progress.

It looks to be just the base destroyer meshes with an additional set of bridge meshes to make it look unique, but presumably they did something different with the structure of that particular file. Judging by the message, this will need to wait for an update of the app.

This app was coded for other Games GR2 files.
The textures are called differently with the GR2 files here.
I'll adjust that along with another correction on the Name numbering.
I was extracting from a GR2 that had 4 meshes all named the same.
So I threw in the quick numbering.
I'll code it to check for duplicate names and add the number only if it's true.

I should add drag and drop someday also.

The LOD model is messed up in the GR2 file so the exports are correct.