Corona Tiles

[Frood]

Wait... what version does BerconMaps show for you? (Mapping rollout lower left) And which DLL/Max version is it?


Good Luck

[Frood]

I was asking because this is puzzling, talking about the plugin for Max2016 (which is the 2015 dll actually):

- While the version readout in the map itself is always "3.01",
- the version from

http://www.ylilammi.com/2013/09/berconmaps/ (named "3.04")

and

https://github.com/Bercon/BerconMaps/tree/master/src/DLL

have the same size but are in fact different at 10 offsets. However we here seem to use the one from github when I compare the hashes and it is working nicely.


Good Luck

[pokoy]

I'm on 3.04 for Max 2016-2019 and they work fine.

Looking at my older downloads, it was around the 2013 version with multiple recompiles and d/l sources.

[Frood]

"3.04"? Is it that what you get in the map rollout?


Good Luck

[pokoy]

"3.04"? Is it that what you get in the map rollout?

No, the zip's name. Honestly I've looked through every Bercon map and couldn't find any info on the version. Where do I find this?!

[Frood]

Create BerconMapping, open "Mapping", lower left. See screenshot... and thanks,


Good Luck

[pokoy]

I see - ouch, it still says 3.01, probably has never been updated to reflect the correct version.

[Frood]

Looks like :-/ Additionally I cannot see anything 3.04 related on GitHub, only 3.03 changes. Again everything obscured in the dark mists of OpenSource - or I'm just too retarded.


Good Luck

[pokoy]

Looks like :-/ Additionally I cannot see anything 3.04 related on GitHub, only 3.03 changes. Again everything obscured in the dark mists of OpenSource - or I'm just too retarded.


Good Luck

I have a few downloads going back to 2015/2016 and the changelog lists 3.04 as the last change. But yeah, BerconMap's history is not really clear to me, it's a bit all over the place.

[romullus]

I very rarely use bercon maps, but from my experience they are anything but stable :/

[pokoy]

I very rarely use bercon maps, but from my experience they are anything but stable :/

I had a lot of crashes in 2012-2014 but since then they are pretty stable for me.
I think there's a problem with the Bercon Gradient, though, where it's easy to crash Max, I remember it was easy to reproduce.

But still, it would be really interesting to learn what exactly doesn't work for those who are affected and which Max/Bercon versions they're on. It might be easier to fix Bercon Maps than it is for the Corona team to write a replacement from scratch.

[steyin]

3.04 is the latest version/recompile, but the 3.01 text within the maps themselves was never changed to reflect updates. I have no issues with IR either. I never really use bercon gradient so I can't speak to its stability, but never had any issues otherwise except for this:

If you are using multitexture with bercontile, and you copy the nodes over to make a new setup, that will usually not only crash MAX, but will make your file unstable where it will crash once you open the material editor. So you have to start from scratch for a new material when using this combo to avoid the issue.

[bishbashross]

I've just done a test on max 2019 and the latest daily build and it is working correctly with IR. Despite still showing an error in the log "Multitexture map in Bercon tile mode is not working with interactive rendering"

[alexyork]

Reviving this topic. It would be brilliant to have a very simple CoronaTileMap, which allows you to plug in a CoronaMultiMap into the tile map slots. In this way you can get lots of randomised maps into a simple tile map. There doesn't appear to be a robust alternative right now other than to give up and model your tiles properly. For super simple surfaces that need randomisation this would save a huge amount of time.

[Jpjapers]

Reviving this topic. It would be brilliant to have a very simple CoronaTileMap, which allows you to plug in a CoronaMultiMap into the tile map slots. In this way you can get lots of randomised maps into a simple tile map. There doesn't appear to be a robust alternative right now other than to give up and model your tiles properly. For super simple surfaces that need randomisation this would save a huge amount of time.

+1 for this. Would be awesome for house bricks too.