NQ-Sirg

Dual universe uses AVX instructions available on all major CPUs since 2011. We don't require AVX2 nor AVX512 because they are not as common.
This is particularly relevant for procedural generation and even on modern machines, it is a valuable optimization which saves the CPU for other things.
We don't do this procedural generation on GPU mostly for numerical determinism. We need the client and the server to generate exactly the same thing. This is typically not possible with GPU computations.
 
Intel 12th gen CPUs come with two kind of cores:
    High performance cores are fast and can handle complex instruction sets like AVX
    Low performance cores are slower and only support a limited instruction set
 
The downside for high performance cores is that they take more space on the chip and they consume more power.
For situations when computing power is not relevant (like IO operations), it makes sense to execute tasks on low performance cores. It also makes sense to have heterogeneous capabilities on your CPU as in the end it translates to a more capable chip using less power (your slow IO operations don’t take precious time from your high performance cores).
 
Note that this kind of architecture is not exactly new and smartphones have been using this approach for years.Now the problem is, that this is kind of new technology for regular personal computers and the support is not completely there yet. Ideally your OS would automatically detect that a specific program needs high performance cores (it does it to a certain extent). In practice, this is not fail-proof yet. From what I could find on the subject and based on feedback I have from Intel, there should be ways for an application to request to run on high performance cores. I’ll try this approach in future months. In the meantime, as suggested by others, there are workarounds to disable the low performance cores

For now, we are in the dark. Some people seem to run the game just fine on 12th gen Intel. Others encounter problems.
 
In this specific thread, we are only talking about issues with 12th gen Intel CPUs. As of now I am not aware of other new CPUs that might have similar issues.

Dual universe uses AVX instructions available on all major CPUs since 2011. We don't require AVX2 nor AVX512 because they are not as common.
This is particularly relevant for procedural generation and even on modern machines, it is a valuable optimization which saves the CPU for other things.
We don't do this procedural generation on GPU mostly for numerical determinism. We need the client and the server to generate exactly the same thing. This is typically not possible with GPU computations.
 
Intel 12th gen CPUs come with two kind of cores:
    High performance cores are fast and can handle complex instruction sets like AVX
    Low performance cores are slower and only support a limited instruction set
 
The downside for high performance cores is that they take more space on the chip and they consume more power.
For situations when computing power is not relevant (like IO operations), it makes sense to execute tasks on low performance cores. It also makes sense to have heterogeneous capabilities on your CPU as in the end it translates to a more capable chip using less power (your slow IO operations don’t take precious time from your high performance cores).
 
Note that this kind of architecture is not exactly new and smartphones have been using this approach for years.Now the problem is, that this is kind of new technology for regular personal computers and the support is not completely there yet. Ideally your OS would automatically detect that a specific program needs high performance cores (it does it to a certain extent). In practice, this is not fail-proof yet. From what I could find on the subject and based on feedback I have from Intel, there should be ways for an application to request to run on high performance cores. I’ll try this approach in future months. In the meantime, as suggested by others, there are workarounds to disable the low performance cores

Bottom line is that it is for the game engine to ensure the correct cores are used for specific tasks. 
 
On can talk about the issue all you want but this is something NQ will need to address and soon (tm) as use of thes ecores will become more and nmore prominent. As I see it, this is not something you can just brush off and make "not a priority right now" unless you very clearly and ufront inform "potential) customers that a sof yet you are not effectively supporting intel 12th gen CPU technology.

Saying "just disable the e-cores when you want to play DU" is not good enough and really is a cop-out to try and push the requirement to deal with this ahead of you. Doing that will only result in it coming back to bite you when for instance GFN mocves to these CPUs to just name something. 

A good reference document would be this:
https://www.intel.com/content/www/us/en/developer/articles/guide/12th-gen-intel-core-processor-gamedev-guide.html
 
 
Also, WIN11 is considerably more efficient and effective with supporting 12th gen CPUs, you should really not use WIN10 on these and I'd say it would be good to have system requirements reflect that if a system runs a 12th core CPU, it need to run Windows 11 to allow you as a dev to only focus on these cpu's running the OS that supports them best.

For now, we are in the dark. Some people seem to run the game just fine on 12th gen Intel. Others encounter problems.
 
In this specific thread, we are only talking about issues with 12th gen Intel CPUs. As of now I am not aware of other new CPUs that might have similar issues.

Dual universe uses AVX instructions available on all major CPUs since 2011. We don't require AVX2 nor AVX512 because they are not as common.
This is particularly relevant for procedural generation and even on modern machines, it is a valuable optimization which saves the CPU for other things.
We don't do this procedural generation on GPU mostly for numerical determinism. We need the client and the server to generate exactly the same thing. This is typically not possible with GPU computations.
 
Intel 12th gen CPUs come with two kind of cores:
    High performance cores are fast and can handle complex instruction sets like AVX
    Low performance cores are slower and only support a limited instruction set
 
The downside for high performance cores is that they take more space on the chip and they consume more power.
For situations when computing power is not relevant (like IO operations), it makes sense to execute tasks on low performance cores. It also makes sense to have heterogeneous capabilities on your CPU as in the end it translates to a more capable chip using less power (your slow IO operations don’t take precious time from your high performance cores).
 
Note that this kind of architecture is not exactly new and smartphones have been using this approach for years.Now the problem is, that this is kind of new technology for regular personal computers and the support is not completely there yet. Ideally your OS would automatically detect that a specific program needs high performance cores (it does it to a certain extent). In practice, this is not fail-proof yet. From what I could find on the subject and based on feedback I have from Intel, there should be ways for an application to request to run on high performance cores. I’ll try this approach in future months. In the meantime, as suggested by others, there are workarounds to disable the low performance cores

Dual universe uses AVX instructions available on all major CPUs since 2011. We don't require AVX2 nor AVX512 because they are not as common.
This is particularly relevant for procedural generation and even on modern machines, it is a valuable optimization which saves the CPU for other things.
We don't do this procedural generation on GPU mostly for numerical determinism. We need the client and the server to generate exactly the same thing. This is typically not possible with GPU computations.
 
Intel 12th gen CPUs come with two kind of cores:
    High performance cores are fast and can handle complex instruction sets like AVX
    Low performance cores are slower and only support a limited instruction set
 
The downside for high performance cores is that they take more space on the chip and they consume more power.
For situations when computing power is not relevant (like IO operations), it makes sense to execute tasks on low performance cores. It also makes sense to have heterogeneous capabilities on your CPU as in the end it translates to a more capable chip using less power (your slow IO operations don’t take precious time from your high performance cores).
 
Note that this kind of architecture is not exactly new and smartphones have been using this approach for years.Now the problem is, that this is kind of new technology for regular personal computers and the support is not completely there yet. Ideally your OS would automatically detect that a specific program needs high performance cores (it does it to a certain extent). In practice, this is not fail-proof yet. From what I could find on the subject and based on feedback I have from Intel, there should be ways for an application to request to run on high performance cores. I’ll try this approach in future months. In the meantime, as suggested by others, there are workarounds to disable the low performance cores

Let's say you had a scan for a given territory. After the update, the scan will still be there in your inventory. It will no longer show you the current underground ore information as this information will now be outdated. Instead it will show you the ore information for the new mining unit feature. So a scan item will still be valid and show relevant information.

Let's say you had a scan for a given territory. After the update, the scan will still be there in your inventory. It will no longer show you the current underground ore information as this information will now be outdated. Instead it will show you the ore information for the new mining unit feature. So a scan item will still be valid and show relevant information.

Let's say you had a scan for a given territory. After the update, the scan will still be there in your inventory. It will no longer show you the current underground ore information as this information will now be outdated. Instead it will show you the ore information for the new mining unit feature. So a scan item will still be valid and show relevant information.

Let's say you had a scan for a given territory. After the update, the scan will still be there in your inventory. It will no longer show you the current underground ore information as this information will now be outdated. Instead it will show you the ore information for the new mining unit feature. So a scan item will still be valid and show relevant information.

Let's say you had a scan for a given territory. After the update, the scan will still be there in your inventory. It will no longer show you the current underground ore information as this information will now be outdated. Instead it will show you the ore information for the new mining unit feature. So a scan item will still be valid and show relevant information.

Let's say you had a scan for a given territory. After the update, the scan will still be there in your inventory. It will no longer show you the current underground ore information as this information will now be outdated. Instead it will show you the ore information for the new mining unit feature. So a scan item will still be valid and show relevant information.