How to add new assets, step by step

[Deliverator]

Well that's an unexpected side effect.
Does Asset Explorer work? (https://iowin.net/en/unity-assets-explorer/) Is it documented anywhere that Asset Studio doesn't work with 2021 or is it just something that people notice?

There are quite a lot of open issues describing the same error that I'm getting. I guess the creator didn't want to fix or maintain it anymore for whatever reason. I'll take a look at Asset Explorer.

 

[Shirotora Kenshin]

Is it because of the latest OW patch? Or did they move to another Unity version before then? I ask because last time i tried AssetStudio export to .fbx, it was successful. As soon as ZBrush has something completed, i will check myself.

 

[Solver]

It's a change on our end - we upgraded to 2021.3 two patches ago.

 

[Shirotora Kenshin]

Ah, yeah, i understand. And now i know why last time the export was successful, because i have a second copy of Old World on Epic Games, where i was not online for several months now. So my Epic copy is not updated, but my Steam copy is, and i am getting errors also with AssetStudio for the Steam copy. I hope Deliverator have success with Asset Explorer.

 

[Deliverator]

Good news! This forked version of Asset Studio can unbundle the latest 2021.3.24 Old World assets and is apparently still in active development for now. There is no latest release on Github so I had to compile myself in VS2022 but we can address that.

 

[Deliverator]

OK. You can grab the latest build of this working version of Asset Studio from here for now:

https://github.com/deliverator23/AssetStudio/suites/13447361125/artifacts/737419206

 

[Shirotora Kenshin]

I kind of knew that you would find a way
This are really good news.

 

[Shirotora Kenshin]

OK. You can grab the latest build of this working version of Asset Studio from here for now:

https://github.com/deliverator23/AssetStudio/suites/13447361125/artifacts/737419206

I as a VS noob managed to build that forked AssetStudio version inside VS 2022, so that it builds out a .exe file (finally, after multiple problems), but i am getting errors in VS, plus the .exe will not do anything

Those are the two errors, if i build AssetStudioGUI:

1. ... \Desktop\AssetStudio-AssetStudioMod\AssetStudioFBXNative\asfbx_anim_context.h(3,10): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "fbxsdk.h": No such file or directory

'Datei (Include) kann nicht geöffnet werden' is german and means: data/file cannot be opened

2. ... Desktop\AssetStudio-AssetStudioMod\AssetStudioGUI\AssetStudioGUI.csproj(79,9): error MSB3030: Datei "C:\Users\ryuto\Desktop\AssetStudio-AssetStudioMod\AssetStudioFBXNative\bin\Win32\Release\AssetStudioFBXNative.dll" konnte nicht kopiert werden, da die Datei nicht gefunden wurde.

'konnte nicht kopiert werden, da die Datei nicht gefunden wurde.' is german and means: could not be copied, because the file could not be found

Hehe, it seems that me and everything related to coding is still not something which works together nicely

Anyways, how was you able to build this AssetStudio version? Are there some steps i have to do first, before i can build the project in VS?

 

[Deliverator]

@Shirotora Kenshin The Asset Studio project is actually configured with a Github workflow that does the compilation into Windows executable which is nice. See the workflows here.

The errors you got are probably because it is necessary to install the FBX SDK as mentioned in the Readme under Build.

 

[Shirotora Kenshin]

@Deliverator Thanks, it was not easy for me, but i have a working AssetStudio now, via the Github method. =)

 

[Deliverator]

@Deliverator Thanks, it was not easy for me, but i have a working AssetStudio now, via the Github method. =)

I will set up a proper release some point soon. Until then this version below should work fine for people I think so no need for people to compile their own:
https://github.com/deliverator23/AssetStudio/suites/13447361125/artifacts/737419206

 

[Dale]

@Deliverator note that as of the recent Test build, you can override UI xml files directly in your mod folder. No need for asset bundling them. Also, the UI xml files have been added to the Reference folder.

 

[Deliverator]

@Shirotora Kenshin OK I'm closing in on completing the description of how to get 3D unit models back and forth between Old World Unity and Blender. There are still some elements of this to describe but sharing what I have in case it is useful.

 

[Shirotora Kenshin]

@Deliverator Cool, i will look into it as soon as possible. Already thank you for all your efforts so far!

Edit: I looked into it, this will already be very helpful. Also good to see that you will address custom 3D static improvements at some point, i guess new Wonders count as improvements.
In the next couple of days i can try to follow your guide step-by-step, starting with adding a 2D image of a new Leader i already made. Thank you again!

 

[Filo90]

any news about 3d assets modification?

 

[Shirotora Kenshin]

any news about 3d assets modification?

I think Deliverator is just busy with reallife, and i am too by the way.
We all need to have patience.

 

[Shirotora Kenshin]

Not that i want to be impatient myself, but Deliverator‘s guide is not complete, though nearly complete… as it seems to me, all that is missing is the last part of implementation for custom 3d units and the process of adding custom 3d improvements plus some kind of patching the animation controllers… and then the guide would be done.

Anyways, i am hoping Deliverator is fine… let me know if i can be helpful. The next week i will have plenty of time to try some things regarding OW modding.
If it‘s helpful, maybe Deliverator could give me a few tips, and then i can try to write the rest of the guide…

 

[Filo90]

It's sad that this game doesn't have a nice modding community, the potential would be huge.

I know that the player base is much smaller than Civ, but still....

Even just a "small" ethnic graphic units pack would be nice for immersion.

 

[Shirotora Kenshin]

Ethnic units sounds cool, but even if we would have a graphics pack, the implementation is the hard part. As far as i know and as of today, no one have figured out completely how we can implement new unit graphics to OW, except of Deliverator. Without a guide, the situation is unlikely to change… it‘s simple as that.

And, in case of ethnic units… i don‘t think it would be possible in OW to have ethnic diversity, unless someone would make some C# stuff to make it possible.

I just can offer to support Deliverator here and there… so that we would have a complete guide in the future.

 

[Filo90]

Devs already told multiple times that they would help coding different aesthetic units for different nations once a 3d assets pack is ready (https://steamcommunity.com/app/597180/discussions/0/4030225100434521497/)

Also, I can't believe that with such nice and supporting devs we still haven't a complete and functional guide to replace 3d assets in game.