Purgator on 12/5/2019 at 00:13
That's looking pretty awesome, J!
john9818a on 12/5/2019 at 03:35
Thanks Purgator! :)
Cardia on 29/5/2019 at 16:01
Nice work there Patrik, i love that tower in the first picture!
Beltzer on 29/5/2019 at 18:55
Thanks. Its a really nice view from up there :)
SneakyGuy101 on 29/5/2019 at 22:23
Beautiful screenshots :eek:
gamophyte on 31/5/2019 at 01:13
Superb Beltzer. It looks like those bricks have bump mapping :)
R Soul on 9/6/2019 at 00:08
For a while I've been using Blender 2.80. There are some improvements but some of the changes mean old addons don't work properly. The .3ds importer/exporter doesn't work, and nor does the Dark Exporter, which also relies on the .3ds exporter. :sweat:
I've updated one of my own addons (a TDM material/texture manager) so I decided to have a go at updating the .3ds addon. In the end the complexity became too much, so I decided to try updating the one Telliamed wrote which imports/exports .e files.
My general approach is to run it and investigate each error that comes up. Sometimes it's just a matter of replacing one line of code with the 2.80 equivalent, other times it's more involved, but so far it's been going well. The original exporter didn't seem to write UV coordinates. There were some functions in there but they no longer work, so I wrote a new one (starting with some code written by someone who wasn't wrong on the internet).
I've been able to create a fully working .e file. If I compare mine with an official one (created from N3ds2e) the UV coord lines don't quite match, yet the object from my .e file looks fine.
I've also implemented an option to apply modifiers to the exported object so a bit of non-destructive modelling can be done
The next thing is to see how it works with jointed objects and vhots.
nicked on 9/6/2019 at 09:18
Oo I haven't updated blender for ages - good to know that the exporter is broken before I do.