Reply to Some questions on FPS, true colour, and the DinkEngine
If you don't have an account, just leave the password field blank.
I've read the message of IvanMZ, and asked DethLord what that FPS was about. Now I know it's frames per second, but I still don't have a clue how that can screw up colours.
So some questions...
1. I press alt + D to check FPS: in DinkEdit or in the game itself?
2. Why is true colour 'wrong' in a D-mod?
3. What has true colour got to do with FPS?
4. What has true colour and FPS have got to do with the DinkEngine?
5. What's the difference between true colour and the Dink Palette?
6. Do many graphics on the same screen have something to do with FPS?
7. I know that adding many graphics in the same screen slows down the loading speed, but if you do have as many as 99 sprites on the screen (placed with the editor) does it screw up all comps? Or only the slow ones?
8. Is there a difference in performance of a computer, of FPS, and of the DinkEngine when placing sprites on screen by using the editor or by using a script to place sprites on screen?
9. Even if you have a fast comp, does the Dink Engine limit the speed of loading when you have many graphics? So, what speed is more important: the DinkEngine or the computer?
10. Can you still not put any new graphics in (with Dink Palette applied of course) even if you have a fast comp, without making sure it's not true colour?
11. DethLord said the Dink Engine is capped around 60-70 FPS. So more FPS's is good? Or is the 28 FPS IvanMZ mentioned good? What IS good? I'd say more FPS is good, but IvanMZ says less FPS is good - well, compared to 60-70 FPS...
12. If I have a new graphic (from one or the other source) what do I have to do to make sure that it doesn't overload the Dink Engine - the FPS and colour part?
13. Is this a problem that only occurs on fast comps? I didn't encounter any colour problem when playing my D-mod (Dink Smallwood's Christmas, that is) and neither did SabreTrout. I don't know the specs of his comp, but mine is real old (300, 32MB, 4 MB videocard.)
14. Any other things I should now on this subject?
Thanks.
So some questions...
1. I press alt + D to check FPS: in DinkEdit or in the game itself?
2. Why is true colour 'wrong' in a D-mod?
3. What has true colour got to do with FPS?
4. What has true colour and FPS have got to do with the DinkEngine?
5. What's the difference between true colour and the Dink Palette?
6. Do many graphics on the same screen have something to do with FPS?
7. I know that adding many graphics in the same screen slows down the loading speed, but if you do have as many as 99 sprites on the screen (placed with the editor) does it screw up all comps? Or only the slow ones?
8. Is there a difference in performance of a computer, of FPS, and of the DinkEngine when placing sprites on screen by using the editor or by using a script to place sprites on screen?
9. Even if you have a fast comp, does the Dink Engine limit the speed of loading when you have many graphics? So, what speed is more important: the DinkEngine or the computer?
10. Can you still not put any new graphics in (with Dink Palette applied of course) even if you have a fast comp, without making sure it's not true colour?
11. DethLord said the Dink Engine is capped around 60-70 FPS. So more FPS's is good? Or is the 28 FPS IvanMZ mentioned good? What IS good? I'd say more FPS is good, but IvanMZ says less FPS is good - well, compared to 60-70 FPS...
12. If I have a new graphic (from one or the other source) what do I have to do to make sure that it doesn't overload the Dink Engine - the FPS and colour part?
13. Is this a problem that only occurs on fast comps? I didn't encounter any colour problem when playing my D-mod (Dink Smallwood's Christmas, that is) and neither did SabreTrout. I don't know the specs of his comp, but mine is real old (300, 32MB, 4 MB videocard.)
14. Any other things I should now on this subject?
Thanks.
