Timeline for Is there more efficient method of terrain rendering in 2D plane than redrawing millions of SDL_FRect each frame
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 10 at 20:15 | comment | added | Questor | DMGregory's idea is how I would do it... Generate a texture using the perlin noise, and then draw a single rect that uses that texture... | |
| Jan 10 at 20:14 | comment | added | Questor | "have, but the performance increase is from 15 fps to 40, which is not a lot" that is about 2.5X faster.. Most people would consider that a major performance increase. | |
| Jan 8 at 21:15 | comment | added | Syntax Error12 | Yes still the issue continues | |
| Jan 8 at 19:54 | comment | added | Kevin | You would draw the data to a texture once, not every frame. | |
| Jan 8 at 8:10 | comment | added | Syntax Error12 | I have, but the performance increase is from 15 fps to 40, which is not a lot. I am sure that the rendering process is the bottleneck. | |
| Jan 7 at 21:45 | comment | added | DMGregory♦ | Have you considered drawing this data to a texture, then just displaying the texture? GPUs are great at sampling textures from transformed coordinates efficiently in parallel. | |
| Jan 7 at 20:09 | history | edited | Syntax Error12 | CC BY-SA 4.0 | added 49 characters in body |
| Jan 7 at 20:07 | history | edited | Syntax Error12 | CC BY-SA 4.0 | added 198 characters in body |
| Jan 7 at 20:03 | history | edited | Syntax Error12 | CC BY-SA 4.0 | edited title |
| Jan 7 at 20:00 | history | edited | Syntax Error12 | CC BY-SA 4.0 | added 155 characters in body |
| S Jan 7 at 19:58 | review | First questions | |||
| Jan 8 at 20:41 | |||||
| S Jan 7 at 19:58 | history | asked | Syntax Error12 | CC BY-SA 4.0 |