FA+
Shop
5815
Views
Views
24
Favorites
Favorites
Category
Flash / All
Species Unspecified / Any
Size 800 x 600
File Size 410.7 kB
Report this content
More from QuoteFox
Flash submissions are emulated via Ruffle. Ruffle is currently in development and compatibility is not guaranteed. Click here for more info.
Dont get too excited, its just a test of how the rougelike renders in flash, I wanted to know how well it performs in a browser and on a website.
Warning, Sending the Cycles to high, may crash your browser.
Feel free to post results bellow,
By pressing right on the keyboard (must click inside the frame first)
You can increase the cycles.
If you want to help, Let me know how many cycles you get before constanty, dropping bellow 20 Fps and what browser your using.
This is alittle stress test of the render engine I made for GROWLF a sexual roguelike im working on, Being ported to flash (hopefully...) Got a long way to go, but we are getting closer by the day. This test is objects being rendered on screen and the cycles is how many times a frame the engine is calculating what to render, at the momment its just selecting a random character to display and in a random position, on the screen. Apose to a actual ingame object/item. In this test the cycles are aprox how many tiles are being rendered in a frame. Im aiming for around 100 cycles a turn (give or take the task being processed within a cycle), but may go to around 300 in heavy populated areas such as towns or dense areas. We will see if thats possible. Any contributions on infomation is apprecated. The Windows version will run alot smoother, no matter what.
Also why 20 fps? well, anything lower then that may cause stalling, and input lag.. and input pileup. No fun.
Warning, Sending the Cycles to high, may crash your browser.
Feel free to post results bellow,
By pressing right on the keyboard (must click inside the frame first)
You can increase the cycles.
If you want to help, Let me know how many cycles you get before constanty, dropping bellow 20 Fps and what browser your using.
This is alittle stress test of the render engine I made for GROWLF a sexual roguelike im working on, Being ported to flash (hopefully...) Got a long way to go, but we are getting closer by the day. This test is objects being rendered on screen and the cycles is how many times a frame the engine is calculating what to render, at the momment its just selecting a random character to display and in a random position, on the screen. Apose to a actual ingame object/item. In this test the cycles are aprox how many tiles are being rendered in a frame. Im aiming for around 100 cycles a turn (give or take the task being processed within a cycle), but may go to around 300 in heavy populated areas such as towns or dense areas. We will see if thats possible. Any contributions on infomation is apprecated. The Windows version will run alot smoother, no matter what.
Also why 20 fps? well, anything lower then that may cause stalling, and input lag.. and input pileup. No fun.
Category Flash / All
Species Unspecified / Any
Size 800 x 600px
File Size 410.7 kB
Running Firefox on Windows 10, here.
The important 20fps mark you wanted;
375 cycles: 21fps average, maintains at least 20.
380 cycles: 20fps average, begins to dip below.
Doesn't begin dipping in to 18fps until over 400 cycles per second.
Some other lower points;
60fps up to 85 cycles per second and down; 90 cycles per second averages about 58fps.
95 cycles: 55fps average.
100 cycles: 53fps average.
110 cycles: 52fps average.
115 cycles: 50fps average.
The important 20fps mark you wanted;
375 cycles: 21fps average, maintains at least 20.
380 cycles: 20fps average, begins to dip below.
Doesn't begin dipping in to 18fps until over 400 cycles per second.
Some other lower points;
60fps up to 85 cycles per second and down; 90 cycles per second averages about 58fps.
95 cycles: 55fps average.
100 cycles: 53fps average.
110 cycles: 52fps average.
115 cycles: 50fps average.
Some torture tests;
520 cycles: 15fps average
820 cycles: 10fps average, input lag is obvious and it starts dropping fast inputs occasionally.
1055 cycles: 5fps average, input lag is obnoxious and fast inputs are dropped constantly. Decided to stop here since this is already not very useful.
520 cycles: 15fps average
820 cycles: 10fps average, input lag is obvious and it starts dropping fast inputs occasionally.
1055 cycles: 5fps average, input lag is obnoxious and fast inputs are dropped constantly. Decided to stop here since this is already not very useful.
165 cycles is when I first saw a dip below 20 fps. 195 is when I no longer saw frames go over 19 fps.
This is on Firefox Quantum 64-bit, running on Windows 10. Additional system stats are a CPU quad i7 920 @ 2.67GHz, 12 GB of memory, and NVidia GTX 970 GPU.
Best of luck with your project!
This is on Firefox Quantum 64-bit, running on Windows 10. Additional system stats are a CPU quad i7 920 @ 2.67GHz, 12 GB of memory, and NVidia GTX 970 GPU.
Best of luck with your project!
Comments