![]() It takes a while to decompress these images before they can be used in rendering. Traditionally these were handled on a single thread, in parallel(ish) to the main thread, but still essentially one at a time.įirestorm 6.4.21 now adds support for doing this in parallel. ![]() It will (by default) check to see how many threads your CPU can support, that’s to say how many jobs it can run concurrently.įrom this it will create a pool of worker threads ready to decode images when they arrive. The more “concurrency” your machine supports the more images it will be able to unpack in parallel. There are a lot of subjective aspects to rendering, things should “feel” snappier but as we are dependent on so many things (disk IO, memory, GPU bandwidth, network fetch) it is not as straightforward as saying things are going to rez twice as quickly.īut we hope you will experience a general uplift in quality. The setting is by default AUTO, this detects the concurrency supported and uses that as a guide. Preferences → Graphics → Hardware Settings → Image Decode Concurrency This is expected to work for the vast majority of systems. N = user specified concurrency (don’t do this unless you really know what you are doing).Īny users that have problems should that have problems should flip the setting to 1 for the old single threaded behaviour.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |