Coding Task List - Before IB2 Initial Release

Discuss anything in general about the IceBlink Engine + Toolset project (or anything else) here.

Re: Coding Task List - Before IB2 Initial Release

Postby youngneil1 » Wed Apr 10, 2019 8:09 pm

IB Beta v150 released - no liabilities, no warranties, use at your own risk:

https://www.dropbox.com/s/8bos3wrenxq65 ... 0.zip?dl=0

- back to old render method for the tiles (well, plus a few minor adjustements), keeping fingers crossed the large tiles work again
User avatar
youngneil1
Backer
Backer
 
Posts: 4935
Joined: Sat Dec 08, 2012 7:51 am

Re: Coding Task List - Before IB2 Initial Release

Postby youngneil1 » Wed Apr 10, 2019 9:08 pm

IB Beta v151 released - no liabilities, no warranties, use at your own risk:

https://www.dropbox.com/s/pzuiyhcr5h087 ... 1.zip?dl=0

- another engine optimization attempt for the brave :roll: : this time I am sorting out all tile layers with t_a_blank filename much earlier; feels very fluid ingame, but who knows which troubles this causes down the line :lol:
User avatar
youngneil1
Backer
Backer
 
Posts: 4935
Joined: Sat Dec 08, 2012 7:51 am

Re: Coding Task List - Before IB2 Initial Release

Postby zach_holbrook » Thu Apr 11, 2019 1:24 am

Yay! I've tested both versions, and neither version alters the big tiles. Also, both seem to improve performance. Finally, the night tiles are working just as expected. Thank you so much for all your hard work! It's really unbelievable. :D :D :D
zach_holbrook
 
Posts: 182
Joined: Mon Dec 26, 2016 5:52 am

Re: Coding Task List - Before IB2 Initial Release

Postby youngneil1 » Thu Apr 11, 2019 5:45 am

Awesome, very happy to hear - that was really helpful feedback uncovering these bugs, much appreciated :) .

Leaving some crazy concept idea for scrolling here, will likely not lead anywhere:

On push of a move button/click move arrow a timer is started running from 100 to 0 and move direction is stored. Until the timer has run out, no other move command is accepted. All tiles, props, party, shadows, floaties... everything on main screen (not ui) is drawn at a position minus or plus gv.SquareSize * timer/100, the affected coordinate component (x,y) as well as the plus/minus nature is determined by the stored move direction. This has to happen at very deep level of the draw hierarchy or too much code would need to be changed (like at drawBitmap and drawText itself). The scrolling will need to be fast or will feel like weird delay. Maybe it will feel wrong anyway :lol: .
User avatar
youngneil1
Backer
Backer
 
Posts: 4935
Joined: Sat Dec 08, 2012 7:51 am

Re: Coding Task List - Before IB2 Initial Release

Postby youngneil1 » Thu Apr 11, 2019 6:12 am

The key/button input would be read in, but all the stuff happening on key down would be blocked unless timer has run out. Maybe all of this would indeed lead to continous scrolling with key held down. Optional walking animations being played while the timer runs would accompany this nicely.
User avatar
youngneil1
Backer
Backer
 
Posts: 4935
Joined: Sat Dec 08, 2012 7:51 am

Re: Coding Task List - Before IB2 Initial Release

Postby youngneil1 » Thu Apr 11, 2019 6:33 am

We night to read in one addditional row/column of tiles for this. Maybe the scanning us generous already now anyway though.
User avatar
youngneil1
Backer
Backer
 
Posts: 4935
Joined: Sat Dec 08, 2012 7:51 am

Re: Coding Task List - Before IB2 Initial Release

Postby youngneil1 » Thu Apr 11, 2019 7:40 am

Trigger and prop interactions would need to be adjusted to only fire once the timer has dropped to zero.

Or maybe do it backwards: only adjust true party position, mover prop position after the timer has run out.

Phew, lots of stuff to consider...
User avatar
youngneil1
Backer
Backer
 
Posts: 4935
Joined: Sat Dec 08, 2012 7:51 am

Re: Coding Task List - Before IB2 Initial Release

Postby youngneil1 » Thu Apr 11, 2019 4:39 pm

Thoughts lost in the wild:
1. Determine target position party
2. Determine target position movers
3. Move (animate) party and movers simulataneously
4. Movement of party shifts whole screen(props, tiles)
5. Movement of props just moves prop gradually
4. Do triggers and prop triggers, using the target positions

Maybe a while loop in doPropTriggers/doTriggers, halting it until timer for camera is zero?
Currently:
Party move
Do prop trigger
Prop move
Do prop trigger (unless called already)
WIP
User avatar
youngneil1
Backer
Backer
 
Posts: 4935
Joined: Sat Dec 08, 2012 7:51 am

Re: Coding Task List - Before IB2 Initial Release

Postby slowdive » Thu Apr 11, 2019 7:00 pm

The joys of trying to optimize one thing and breaking the other parts :lol: sounds very familiar to me and my attempts at optimization. It is all worth it in the end though if it gets figured out. Love hearing all the progress by Zach and Karl on the module and engine, very inspiring and exciting. House is going back on the market in days so fun times here again.
User avatar
slowdive
Site Admin
Site Admin
 
Posts: 3115
Joined: Wed Nov 21, 2012 11:58 pm

Re: Coding Task List - Before IB2 Initial Release

Postby youngneil1 » Fri Apr 12, 2019 8:44 am

Optimization is a bit scary as deeply rooted changes affect so many different parts of the code :o. Like, aeh, brain surgery :lol: .

Keeping fingers crossed for the sale of the house :) !

I think I will have a go at scrolling with a prototype here. I see so many places where it can easily all go down in flames, but if it would work out against all odds, it would be really nice. So, what's to lose in trying 8-) , harf! Yeah, yeah, sleep, hair color, social relations, muscles, sanity... the usual suspects :lol: .
User avatar
youngneil1
Backer
Backer
 
Posts: 4935
Joined: Sat Dec 08, 2012 7:51 am

PreviousNext

Return to General IceBlink Project Discussions

Who is online

Users browsing this forum: No registered users and 3 guests