Thread
ThemePark Development Status Updates
Hey Themers!
This is just a quick note to let everyone know that I'm winding up the work on my current software development project, meaning that the modifications to ThemePark that were being discussed a few months ago are now my top priority. If you'd like a recap, here is the old thread.
I'll probably post in this thread about any exciting milestones.
Thanks for your patience!
P.S. Report bugs!
This is just a quick note to let everyone know that I'm winding up the work on my current software development project, meaning that the modifications to ThemePark that were being discussed a few months ago are now my top priority. If you'd like a recap, here is the old thread.
I'll probably post in this thread about any exciting milestones.
Thanks for your patience!
P.S. Report bugs!
I was *just* wondering about this earlier... glad to hear it's underway now, can't wait!
Keep up the great work
-Carbon
Keep up the great work
-Carbon
That's cool!
I still use Sprocket for the most part because it's way faster than ThemePark. But I do use ThemePark for resizing resouces and editing PPATs.
I have noted one small bug in the PPAT editor. When it displays the tiled pattern below, it show the pattern upsidedown. Maybe this only happened at one perticular time.
And sometimes when I look at the preview of a PXM, it will looked blurred even though the sliders is at "1x".
Will the new version be any faster?
I still use Sprocket for the most part because it's way faster than ThemePark. But I do use ThemePark for resizing resouces and editing PPATs.
I have noted one small bug in the PPAT editor. When it displays the tiled pattern below, it show the pattern upsidedown. Maybe this only happened at one perticular time.
And sometimes when I look at the preview of a PXM, it will looked blurred even though the sliders is at "1x".
Will the new version be any faster?
Quote:
|
Originally posted by bOOzo: I have noted one small bug in the PPAT editor. When it displays the tiled pattern below, it show the pattern upsidedown. Maybe this only happened at one perticular time. |
I think you forgot to post the "pattern below".

I seem to recall fixing this bug for 1.0b9, but I'm not sure. Have you tried it recently?
Quote:
| And sometimes when I look at the preview of a PXM, it will looked blurred even though the sliders is at "1x". |
I haven't seen this. Can you give me steps to reproduce it?
Quote:
| Will the new version be any faster? |
Well, I've gotten rid of a large speed bottleneck in the existing code that will automatically be picked up in the new code. This will make moving from on PXM to another about 50% faster (it was a big speed bottleneck).
Quote:
|
Originally posted by smeger: I think you forgot to post the "pattern below". ![]() I seem to recall fixing this bug for 1.0b9, but I'm not sure. Have you tried it recently? I haven't seen this. Can you give me steps to reproduce it? Well, I've gotten rid of a large speed bottleneck in the existing code that will automatically be picked up in the new code. This will make moving from on PXM to another about 50% faster (it was a big speed bottleneck). |
Here is a picture to illustrate what I mean:

The blur thing might only happen at that size, but I'm not sure.
The ppat might be a special case because I copied the ppats from a k-scheme and edited them in themepark.
Glad to hear that the new version will be faster
Quote:
|
Originally posted by smeger: I haven't seen this. Can you give me steps to reproduce it? |
I get this as well - there seems to be some sort of resampling happening at 1:1... it's almost as if the method used to smooth the image as it's scaled up and down is having an effect on the 1:1 image. It also seems to happen with every pxm. although it doesn't seem to happen with ppats