double buffer and autoback tilemap answer issue
1 Attachment(s)
Hello
I create a map editor on AMOSPRO. I coded everything myself, even the silder. I use drawing instructions (box, bar, plot) for the sliders and grid, a bob for the arrow and a sprite for the map cursor. I find it extremely slow to display the map in a 34*34 plot it takes several seconds. I have tried double buffering, autoback, nothing I have found a solution. WINUAE 68020 + fast... or 68030 the fastest is the same. ' Dungeon crawler by DarkN3mo |
How long does it take to draw 20*16
double buffer will obviously be slower take a look at an existing map editor like Tome or the excellent Mac Map for comparison. |
Quote:
20*16 about 2 seconds I know there are other editors but I prefer to code all my own utilities. I'm not sure how to do this, but I'm not sure I know how to do it. |
Yeah good idea but just for comparison.
If you load it into a Dim variable it might speed it up but I agree 2 seconds seems a bit long. print command is also a weakest link it's very slow remove it. |
Quote:
not necessarily the goal, because in binary you consume less space. ok TEXT command is faster. |
iirc Text and other bar, line etc are very slow
most stuff like this removing print will be significantly faster but for a map editor it's not a big deal but for a game you should look to replace text with Paste bob or better Paste Icon. |
Quote:
yes of course, for the game I'll use bob sprite and bitmap text. for the map, I redraw the map each time I change the slider, to take into account the offset, I have no choice my editor will be usable in the end for several types of games on the other hand, I'm currently making an old school Dungeon crawler engine (Dungeon Master like) It's going pretty well. If you have any ideas I'm interested :) I'll share the progress on the forum I've taken up the Amos again after more than 20 years off, argh! |
I have no idea about that type of game but iirc they did something with Bloodwych? on the Amos factory maybe those guys can help.
instead of redrawing the map use Screen offset to scroll, hardware scrolling is always the fastest method to scroll. O and good luck! |
Quote:
Yes I know but this would mean drawing the whole map on another screen which can take up a lot of chip space if the map is large. but that's something to consider too. thanks |
more complex Hardware scrolling called wrap around or corkscrew means you can have a smaller screen and hardware scroll endlessly but gets more complex.
you can also use the old software scrolling with Screen Copy I never liked this and don't know if it would be faster than redrawing the whole screen but it was commonly used, Tome used it. also there's a turbo extension that can paste Icons even quicker but I had some problems using it and Double Buffering but I only looked briefly but it is faster. |
Actually, Tome didn't use it. The culprit is that the blitter clocks at only 3.5 MHz with 16 bit bus accesses. Even on AGA.
|
I never really looked but iirc nearly all the Tome examples used screen copy for scrolling like these https://m.youtube.com/watch?v=8jbf-cSvPOg
|
Screen copy uses large blitter operations. Very expensive. Screen scroll uses screen offsets and the copper for almost no time cost.
|
Screen offset is the command is the command built into Amos that allows smooth hardware scrolling all the Tome commands for scrolling and Screen copy are very slow.
If you look at the Tome examples there mainly based on very small screens because of this, there also very jerky unlike the Screen Offset command. |
Quote:
https://www.youtube.com/watch?v=3egJx4ne_cw :cool |
All times are GMT +2. The time now is 02:43. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.