Other World Mapper Forum

I had only OWM open and let it generate the shorelines. It did used multiple cores/threads, but #11 + #12 are used alternately, just like #9 + #10.

In summery the utilisation was between 12-16%.
The screenshot was shot after 2 minutes in the process.

Since the shorelines are generated in the backgroud it's fine, that it takes a while. But if the process can be speed up, it would be nice :)

Balmung wrote: ↑

Wed Apr 07, 2021 5:09 pm

I had only OWM open and let it generate the shorelines. It did used multiple cores/threads, but #11 + #12 are used alternately, just like #9 + #10.

In summery the utilisation was between 12-16%.
The screenshot was shot after 2 minutes in the process.

Since the shorelines are generated in the backgroud it's fine, that it takes a while. But if the process can be speed up, it would be nice

I'll have to revisit, but I think CPU utilization is around as much as Windows will allow for background threads. The algorithm in general could probably be optimized some, but that type of vector is something that our engine should probably move to the GPU........

- Alejandro