11-01-2018, 03:38 AM
(This post was last modified: 11-01-2018, 05:14 AM by Richard Kain.)
It wasn't nearly as hard as I had thought it would be. And you do put a sizable number of comments in your code, which makes it a bit easier to follow. Also, Unity has supported the importing and use of third-party pre-compiled libraries for a while, and there are a sizable number of tutorials for doing that, even if they aren't specific to Tilengine.
I might give compiling Tilengine for iOS a try, I keep a Mac Mini around for iOS and Mac development. Ideally, it would be great to cook up a Swift 4 binding, but I shouldn't get ahead of myself. But it will have to wait until a little later in the year. I'm very busy with some home repairs, and a trip coming up, and of course the holiday season is fast approaching. I was able to sort out exporting 8-bit pngs from GIMP properly, so my asset pipeline for Tilengine has firmed up. And I've played around with dynamic palette generation and assignment, which has been going very well.
Also, the C# binding I was using didn't actually have an UpdateFrame function. But I've learned enough that I was able to add one, and took your suggestion about using that function instead of a for loop in the Update function. It worked great. I might look into using the separate thread approach to getting a Tilengine context when running the engine in the Unity Editor environment. I think that might help with a few of the issues I was running into.
I might give compiling Tilengine for iOS a try, I keep a Mac Mini around for iOS and Mac development. Ideally, it would be great to cook up a Swift 4 binding, but I shouldn't get ahead of myself. But it will have to wait until a little later in the year. I'm very busy with some home repairs, and a trip coming up, and of course the holiday season is fast approaching. I was able to sort out exporting 8-bit pngs from GIMP properly, so my asset pipeline for Tilengine has firmed up. And I've played around with dynamic palette generation and assignment, which has been going very well.
Also, the C# binding I was using didn't actually have an UpdateFrame function. But I've learned enough that I was able to add one, and took your suggestion about using that function instead of a for loop in the Update function. It worked great. I might look into using the separate thread approach to getting a Tilengine context when running the engine in the Unity Editor environment. I think that might help with a few of the issues I was running into.