Possible common denominator for the performance issues

[Wonko_The_Sane]

True but why is the same code buggier on some machines than others?

Because of computer configurations. Saying that the machines have the same processors, amount of ram, and video card does not mean they are equal.
Is the ram configured as dual channel? How many other things are sharing the PCIe channels with the video card? Does the processor have adequate cooling?
All of those things will impact performance.

 

[Joe Akeem]

Ryzen 5 2600x, 1060 6gb, 16gb RAM. MSI Tomahawk B450, Win 10 version 20H2 64bit, in BIOS SMT (simultaneous multithreading): ON

Horizons all HIGH and SS at 1.5 (due to abyssmal AA) = steady 60fps everywhere
Oddyssey all MID no SS = 60 in space, 40 in concourse (legs), 25-35 at populated settlements (legs)

Gonna try with SMT OFF according to this:

https://www.reddit.com/r/playrust/comments/bg1s9q

Source: https://www.reddit.com/r/playrust/comments/bg1s9q/psa_for_ryzen_users_disable_smt/

 

[m0rl0ck]

The common denominators are incompetence, lack of testing, and lust for a quick buck before the yearly financials. Seriously, lets keep it real.

 

[Ancient Forester]

Because of computer configurations. Saying that the machines have the same processors, amount of ram, and video card does not mean they are equal.
Is the ram configured as dual channel? How many other things are sharing the PCIe channels with the video card? Does the processor have adequate cooling?
All of those things will impact performance.

This. As I included in this thread : https://forums.frontier.co.uk/threads/hotfix-0002-subjective-experience.576885/#post-9193108 Settings such as hyperthreading and enabling of VT instructions make impact. Which memory slots are enabled make impact. Not all manufacturers of videoboards use reference designs and clocks. Nor do all mainboard versions of the same base chipset use the same manufacturer chips for support functions. Included screenshots from cpu-z show the kind of information a developer will actually need (the portable zip from CPU-ID is sufficient. It's safe) to know what systems are actually used. Obtw, this software can also detect the individual memory dimm maker, and if you're running them on correct speed. I only included one of the four populated slots.

 

[Ancient Forester]

Ryzen 5 2600x, 1060 6gb, 16gb RAM. MSI Tomahawk B450, Win 10 version 20H2 64bit, in BIOS SMT (simultaneous multithreading): ON

Horizons all HIGH and SS at 1.5 (due to abyssmal AA) = steady 60fps everywhere
Oddyssey all MID no SS = 60 in space, 40 in concourse (legs), 25-35 at populated settlements (legs)

Gonna try with SMT OFF according to this:

https://www.reddit.com/r/playrust/comments/bg1s9q

Source: https://www.reddit.com/r/playrust/comments/bg1s9q/psa_for_ryzen_users_disable_smt/

That may well be true for Rust (I haven't touched it myself) a game I hear has about ZERO multithreading. For Elite it's not the case. As you can see it balances almost perfectly (an impressive programming feat). These three are from when I did the horizons-vs-odyssey-with-studio-vs-gameready driver test in the other thread. I can also mention that for COD:MW (before the BR nightmare ruined a good game), if you DIDN'T run hyperthreading, odds are you would experience so high input lag the game would be literally uncontrollable (as in ignoring your keypresses). So hyperthreading/multithreading on or off is a per game thing if you ONLY run games. If you run other things in addition (such as a streaming software): Leave it on.

 

[Ancient Forester]

The common denominators are incompetence, lack of testing, and lust for a quick buck before the yearly financials. Seriously, lets keep it real.

That may well be, but this is a technical discussion, and your argument fails to meet the topic. Thanks for your participation.

 

[Cmdr Alphonso Dementia]

Interesting - I fall into the AMD Ryzen X570 category and am used to running Horizons at 1440p on Ultra and smiling happily at my 100+ FPS at all times.

With Odyssey, I have had to turn things way down - a mix of Medium/High settings. Ultra is like a slideshow.

I have a computer that I put together myself about 5 years ago. I7-4790, 32GB RAM, GTX 1660 card. Odyssey runs smooth as glass, although I have not checked the actual frame rate. Ultra settings across the board.
I know... I can hardly believe it myself.

 

[Ancient Forester]

I have a computer that I put together myself about 5 years ago. I7-4790, 32GB RAM, GTX 1660 card. Odyssey runs smooth as glass, although I have not checked the actual frame rate...

I7-4790 is a Haswell processor (Socket LGA1xxx series), which are among those I originally suspected of running well. But thank you for reporting this you are doing EXACTLY what I hope for. You list components, and state ok or not. <3

 

[Ancient Forester]

I have a computer that I put together myself about 5 years ago. I7-4790, 32GB RAM, GTX 1660 card. Odyssey runs smooth as glass, although I have not checked the actual frame rate. Ultra settings across the board.
I know... I can hardly believe it myself.

A bit of extra praise. Getting to know what combinations work ok is just as important as knowing what combinations fail. ALL data points here are of interest.

So again thanks. You are making this easier for everybody, and you ARE improving chances that we can get this back on track.

 

[Ancient Forester]

Oh, and I'm wokring on making a little powershell applet for us that collects the relevant data ready to paste into a post. It won't be pretty, but atleast it will give the developers the system baseboard information and gpu information. For this laptop I'm using from bed (having a bad pain day, don't ask), the uglybugly output woud be like this:

PS C:\WINDOWS\system32> Get-WmiObject win32_baseboard; Get-WmiObject Win32_Bios; Get-WmiObject win32_physicalmemory | Select Manufacturer,Banklabel,Configuredclockspeed,Devicelocator,Capacity,Serialnumber; Get-ComputerInfo OSName, OsArchitecture; Get-WmiObject win32_VideoController​

​

Manufacturer : Microsoft Corporation Model : Name : Base Board SerialNumber : A12353720125927A​

SKU :​

Product : Surface Book 2​

​

SMBIOSBIOSVersion : 390.3681.768​

Manufacturer : Microsoft Corporation​

Name : 390.3681.768​

SerialNumber : 008942592857​

Version : MSFT - 0​

​

Manufacturer : SK Hynix​

Banklabel : BANK 0​

Configuredclockspeed : 1867​

Devicelocator : ChannelA-DIMM0​

Capacity : 8589934592​

Serialnumber : 00000000​

​

Manufacturer : SK Hynix​

Banklabel : BANK 2​

Configuredclockspeed : 1867​

Devicelocator : ChannelB-DIMM0​

Capacity : 8589934592​

Serialnumber : 00000000​

​

OsName : Microsoft Windows 10 Pro​

OsArchitecture : 64-bit​

​

__GENUS : 2​

__CLASS : Win32_VideoController​

__SUPERCLASS : CIM_PCVideoController​

__DYNASTY : CIM_ManagedSystemElement​

__RELPATH : Win32_VideoController.DeviceID="VideoController1"​

__PROPERTY_COUNT : 59​

__DERIVATION : {CIM_PCVideoController, CIM_VideoController, CIM_Controller, CIM_LogicalDevice...}​

__SERVER : FENRIS​

__NAMESPACE : root\cimv2​

__PATH : \\FENRIS\root\cimv2:Win32_VideoController.DeviceID="VideoController1"​

AcceleratorCapabilities :​

AdapterCompatibility : Intel Corporation​

AdapterDACType : Internal​

AdapterRAM : 1073741824​

Availability : 3​

CapabilityDescriptions :​

Caption : Intel(R) UHD Graphics 620​

ColorTableEntries :​

ConfigManagerErrorCode : 0​

ConfigManagerUserConfig : False​

CreationClassName : Win32_VideoController​

CurrentBitsPerPixel : 32​

CurrentHorizontalResolution : 3000​

CurrentNumberOfColors : 4294967296​

CurrentNumberOfColumns : 0​

CurrentNumberOfRows : 0​

CurrentRefreshRate : 59​

CurrentScanMode : 4​

CurrentVerticalResolution : 2000​

Description : Intel(R) UHD Graphics 620​

DeviceID : VideoController1​

DeviceSpecificPens :​

DitherType : 0​

DriverDate : 20200906000000.000000-000​

DriverVersion : 27.20.100.8682​

ErrorCleared :​

ErrorDescription :​

ICMIntent :​

ICMMethod :​

InfFilename : oem70.inf​

InfSection : iKBLD_w10_DS​

InstallDate :​

InstalledDisplayDrivers : C:\WINDOWS\System32\DriverStore\FileRepository\64zh8682.inf_amd64_ad04d90b4a2ec5da\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\64zh8682.inf_amd64_ad04d90b4a2ec5da\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\64zh8682.inf_amd64_ad04d90b4a2ec5da\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileReposito​

ry\64zh8682.inf_amd64_ad04d90b4a2ec5da\igd12umd64.dll​

LastErrorCode :​

MaxMemorySupported :​

MaxNumberControlled :​

MaxRefreshRate : 59​

MinRefreshRate : 59​

Monochrome : False​

Name : Intel(R) UHD Graphics 620​

NumberOfColorPlanes :​

NumberOfVideoPages :​

PNPDeviceID : PCI\VEN_8086&DEV_5917&SUBSYS_00271414&REV_07\3&11583659&0&10​

PowerManagementCapabilities :​

PowerManagementSupported :​

ProtocolSupported :​

ReservedSystemPaletteEntries :​

SpecificationVersion :​

Status : OK​

StatusInfo :​

SystemCreationClassName : Win32_ComputerSystem​

SystemName : FENRIS​

SystemPaletteEntries :​

TimeOfLastReset :​

VideoArchitecture : 5​

VideoMemoryType : 2​

VideoMode :​

VideoModeDescription : 3000 x 2000 x 4294967296 colors​

VideoProcessor : Intel(R) UHD Graphics Family​

PSComputerName : FENRIS​

​

__GENUS : 2​

__CLASS : Win32_VideoController​

__SUPERCLASS : CIM_PCVideoController​

__DYNASTY : CIM_ManagedSystemElement​

__RELPATH : Win32_VideoController.DeviceID="VideoController2"​

__PROPERTY_COUNT : 59​

__DERIVATION : {CIM_PCVideoController, CIM_VideoController, CIM_Controller, CIM_LogicalDevice...}​

__SERVER : FENRIS​

__NAMESPACE : root\cimv2​

__PATH : \\FENRIS\root\cimv2:Win32_VideoController.DeviceID="VideoController2"​

AcceleratorCapabilities :​

AdapterCompatibility : NVIDIA​

AdapterDACType : Integrated RAMDAC​

AdapterRAM : 2147483648​

Availability : 8​

CapabilityDescriptions :​

Caption : NVIDIA GeForce GTX 1050​

ColorTableEntries :​

ConfigManagerErrorCode : 0​

ConfigManagerUserConfig : False​

CreationClassName : Win32_VideoController​

CurrentBitsPerPixel :​

CurrentHorizontalResolution :​

CurrentNumberOfColors :​

CurrentNumberOfColumns :​

CurrentNumberOfRows :​

CurrentRefreshRate :​

CurrentScanMode :​

CurrentVerticalResolution :​

Description : NVIDIA GeForce GTX 1050​

DeviceID : VideoController2​

DeviceSpecificPens :​

DitherType :​

DriverDate : 20210506000000.000000-000​

DriverVersion : 27.21.14.6259​

ErrorCleared :​

ErrorDescription :​

ICMIntent :​

ICMMethod :​

InfFilename : oem12.inf​

InfSection : Section005​

InstallDate :​

InstalledDisplayDrivers : C:\WINDOWS\System32\DriverStore\FileRepository\nvmsosi.inf_amd64_1002529af2df1be1\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmsosi.inf_amd64_1002529af2df1be1\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmsosi.inf_amd64_1002529af2df1be1\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmsosi.​

inf_amd64_1002529af2df1be1\nvldumdx.dll​

LastErrorCode :​

MaxMemorySupported :​

MaxNumberControlled :​

MaxRefreshRate :​

MinRefreshRate :​

Monochrome : False​

Name : NVIDIA GeForce GTX 1050​

NumberOfColorPlanes :​

NumberOfVideoPages :​

PNPDeviceID : PCI\VEN_10DE&DEV_1C8D&SUBSYS_00241414&REV_A1\4&3B87FCA8&0&00E4​

PowerManagementCapabilities :​

PowerManagementSupported :​

ProtocolSupported :​

ReservedSystemPaletteEntries :​

SpecificationVersion :​

Status : OK​

StatusInfo :​

SystemCreationClassName : Win32_ComputerSystem​

SystemName : FENRIS​

SystemPaletteEntries :​

TimeOfLastReset :​

VideoArchitecture : 5​

VideoMemoryType : 2​

VideoMode :​

VideoModeDescription :​

VideoProcessor : GeForce GTX 1050​

PSComputerName : FENRIS​

​

​

​

PS C:\WINDOWS\system32>​

As I said: Not pretty.

 

[Ancient Forester]

Oh, and I'm wokring on making a little powershell applet for us that collects the relevant data ready to paste into a post. It won't be pretty, but atleast it will give the developers the system baseboard information and gpu information. For this laptop I'm using from bed (having a bad pain day, don't ask), the uglybugly output woud be like this:

PS C:\WINDOWS\system32> Get-WmiObject win32_baseboard; Get-WmiObject Win32_Bios; Get-WmiObject win32_physicalmemory | Select Manufacturer,Banklabel,Configuredclockspeed,Devicelocator,Capacity,Serialnumber; Get-ComputerInfo OSName, OsArchitecture; Get-WmiObject win32_VideoController​

​

Manufacturer : Microsoft Corporation Model : Name : Base Board SerialNumber : A12353720125927A​

SKU :​

Product : Surface Book 2​

​

SMBIOSBIOSVersion : 390.3681.768​

Manufacturer : Microsoft Corporation​

Name : 390.3681.768​

SerialNumber : 008942592857​

Version : MSFT - 0​

​

Manufacturer : SK Hynix​

Banklabel : BANK 0​

Configuredclockspeed : 1867​

Devicelocator : ChannelA-DIMM0​

Capacity : 8589934592​

Serialnumber : 00000000​

​

Manufacturer : SK Hynix​

Banklabel : BANK 2​

Configuredclockspeed : 1867​

Devicelocator : ChannelB-DIMM0​

Capacity : 8589934592​

Serialnumber : 00000000​

​

OsName : Microsoft Windows 10 Pro​

OsArchitecture : 64-bit​

​

__GENUS : 2​

__CLASS : Win32_VideoController​

__SUPERCLASS : CIM_PCVideoController​

__DYNASTY : CIM_ManagedSystemElement​

__RELPATH : Win32_VideoController.DeviceID="VideoController1"​

__PROPERTY_COUNT : 59​

__DERIVATION : {CIM_PCVideoController, CIM_VideoController, CIM_Controller, CIM_LogicalDevice...}​

__SERVER : FENRIS​

__NAMESPACE : root\cimv2​

__PATH : \\FENRIS\root\cimv2:Win32_VideoController.DeviceID="VideoController1"​

AcceleratorCapabilities :​

AdapterCompatibility : Intel Corporation​

AdapterDACType : Internal​

AdapterRAM : 1073741824​

Availability : 3​

CapabilityDescriptions :​

Caption : Intel(R) UHD Graphics 620​

ColorTableEntries :​

ConfigManagerErrorCode : 0​

ConfigManagerUserConfig : False​

CreationClassName : Win32_VideoController​

CurrentBitsPerPixel : 32​

CurrentHorizontalResolution : 3000​

CurrentNumberOfColors : 4294967296​

CurrentNumberOfColumns : 0​

CurrentNumberOfRows : 0​

CurrentRefreshRate : 59​

CurrentScanMode : 4​

CurrentVerticalResolution : 2000​

Description : Intel(R) UHD Graphics 620​

DeviceID : VideoController1​

DeviceSpecificPens :​

DitherType : 0​

DriverDate : 20200906000000.000000-000​

DriverVersion : 27.20.100.8682​

ErrorCleared :​

ErrorDescription :​

ICMIntent :​

ICMMethod :​

InfFilename : oem70.inf​

InfSection : iKBLD_w10_DS​

InstallDate :​

InstalledDisplayDrivers : C:\WINDOWS\System32\DriverStore\FileRepository\64zh8682.inf_amd64_ad04d90b4a2ec5da\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\64zh8682.inf_amd64_ad04d90b4a2ec5da\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\64zh8682.inf_amd64_ad04d90b4a2ec5da\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileReposito​

ry\64zh8682.inf_amd64_ad04d90b4a2ec5da\igd12umd64.dll​

LastErrorCode :​

MaxMemorySupported :​

MaxNumberControlled :​

MaxRefreshRate : 59​

MinRefreshRate : 59​

Monochrome : False​

Name : Intel(R) UHD Graphics 620​

NumberOfColorPlanes :​

NumberOfVideoPages :​

PNPDeviceID : PCI\VEN_8086&DEV_5917&SUBSYS_00271414&REV_07\3&11583659&0&10​

PowerManagementCapabilities :​

PowerManagementSupported :​

ProtocolSupported :​

ReservedSystemPaletteEntries :​

SpecificationVersion :​

Status : OK​

StatusInfo :​

SystemCreationClassName : Win32_ComputerSystem​

SystemName : FENRIS​

SystemPaletteEntries :​

TimeOfLastReset :​

VideoArchitecture : 5​

VideoMemoryType : 2​

VideoMode :​

VideoModeDescription : 3000 x 2000 x 4294967296 colors​

VideoProcessor : Intel(R) UHD Graphics Family​

PSComputerName : FENRIS​

​

__GENUS : 2​

__CLASS : Win32_VideoController​

__SUPERCLASS : CIM_PCVideoController​

__DYNASTY : CIM_ManagedSystemElement​

__RELPATH : Win32_VideoController.DeviceID="VideoController2"​

__PROPERTY_COUNT : 59​

__DERIVATION : {CIM_PCVideoController, CIM_VideoController, CIM_Controller, CIM_LogicalDevice...}​

__SERVER : FENRIS​

__NAMESPACE : root\cimv2​

__PATH : \\FENRIS\root\cimv2:Win32_VideoController.DeviceID="VideoController2"​

AcceleratorCapabilities :​

AdapterCompatibility : NVIDIA​

AdapterDACType : Integrated RAMDAC​

AdapterRAM : 2147483648​

Availability : 8​

CapabilityDescriptions :​

Caption : NVIDIA GeForce GTX 1050​

ColorTableEntries :​

ConfigManagerErrorCode : 0​

ConfigManagerUserConfig : False​

CreationClassName : Win32_VideoController​

CurrentBitsPerPixel :​

CurrentHorizontalResolution :​

CurrentNumberOfColors :​

CurrentNumberOfColumns :​

CurrentNumberOfRows :​

CurrentRefreshRate :​

CurrentScanMode :​

CurrentVerticalResolution :​

Description : NVIDIA GeForce GTX 1050​

DeviceID : VideoController2​

DeviceSpecificPens :​

DitherType :​

DriverDate : 20210506000000.000000-000​

DriverVersion : 27.21.14.6259​

ErrorCleared :​

ErrorDescription :​

ICMIntent :​

ICMMethod :​

InfFilename : oem12.inf​

InfSection : Section005​

InstallDate :​

InstalledDisplayDrivers : C:\WINDOWS\System32\DriverStore\FileRepository\nvmsosi.inf_amd64_1002529af2df1be1\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmsosi.inf_amd64_1002529af2df1be1\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmsosi.inf_amd64_1002529af2df1be1\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvmsosi.​

inf_amd64_1002529af2df1be1\nvldumdx.dll​

LastErrorCode :​

MaxMemorySupported :​

MaxNumberControlled :​

MaxRefreshRate :​

MinRefreshRate :​

Monochrome : False​

Name : NVIDIA GeForce GTX 1050​

NumberOfColorPlanes :​

NumberOfVideoPages :​

PNPDeviceID : PCI\VEN_10DE&DEV_1C8D&SUBSYS_00241414&REV_A1\4&3B87FCA8&0&00E4​

PowerManagementCapabilities :​

PowerManagementSupported :​

ProtocolSupported :​

ReservedSystemPaletteEntries :​

SpecificationVersion :​

Status : OK​

StatusInfo :​

SystemCreationClassName : Win32_ComputerSystem​

SystemName : FENRIS​

SystemPaletteEntries :​

TimeOfLastReset :​

VideoArchitecture : 5​

VideoMemoryType : 2​

VideoMode :​

VideoModeDescription :​

VideoProcessor : GeForce GTX 1050​

PSComputerName : FENRIS​

​

​

​

PS C:\WINDOWS\system32>​

As I said: Not pretty.

Similar output on my Elite-playing PC:

PS C:\Windows\system32> Get-WmiObject win32_baseboard; Get-WmiObject Win32_Bios; Get-WmiObject win32_physicalmemory | Select Manufacturer,Banklabel,Configuredclockspeed,Devicelocator,Capacity,Serialnumber; Get-ComputerInfo OSName, OsArchitecture; Get-WmiObject win32_VideoController​

​

Manufacturer : ASUSTeK COMPUTER INC.​

Model :​

Name : Base Board​

SerialNumber : 130915858000055​

SKU :​

Product : P9X79​

​

SMBIOSBIOSVersion : 4801​

Manufacturer : American Megatrends Inc.​

Name : 4801​

SerialNumber : System Serial Number​

Version : ALASKA - 1072009​

​

Manufacturer : Kingston​

Banklabel : ChannelA​

Configuredclockspeed : 1866​

Devicelocator : ChannelA_Dimm1​

Capacity : 8589934592​

Serialnumber : 15047714​

​

Manufacturer : Kingston​

Banklabel : ChannelB​

Configuredclockspeed : 1866​

Devicelocator : ChannelB_Dimm1​

Capacity : 8589934592​

Serialnumber : 15046114​

​

Manufacturer : Kingston​

Banklabel : ChannelC​

Configuredclockspeed : 1866​

Devicelocator : ChannelC_Dimm1​

Capacity : 8589934592​

Serialnumber : 18048F14​

​

Manufacturer : Kingston​

Banklabel : ChannelD​

Configuredclockspeed : 1866​

Devicelocator : ChannelD_Dimm1​

Capacity : 8589934592​

Serialnumber : 1C049714​

​

OsName : Microsoft Windows 10 Pro​

OsArchitecture : 64-bit​

​

__GENUS : 2​

__CLASS : Win32_VideoController​

__SUPERCLASS : CIM_PCVideoController​

__DYNASTY : CIM_ManagedSystemElement​

__RELPATH : Win32_VideoController.DeviceID="VideoController1"​

__PROPERTY_COUNT : 59​

__DERIVATION : {CIM_PCVideoController, CIM_VideoController, CIM_Controller, CIM_LogicalDevice...}​

__SERVER : PHOBOS​

__NAMESPACE : root\cimv2​

__PATH : \\PHOBOS\root\cimv2:Win32_VideoController.DeviceID="VideoController1"​

AcceleratorCapabilities :​

AdapterCompatibility : NVIDIA​

AdapterDACType : Integrated RAMDAC​

AdapterRAM : 4293918720​

Availability : 3​

CapabilityDescriptions :​

Caption : NVIDIA GeForce GTX 1660 SUPER​

ColorTableEntries :​

ConfigManagerErrorCode : 0​

ConfigManagerUserConfig : False​

CreationClassName : Win32_VideoController​

CurrentBitsPerPixel : 32​

CurrentHorizontalResolution : 2560​

CurrentNumberOfColors : 4294967296​

CurrentNumberOfColumns : 0​

CurrentNumberOfRows : 0​

CurrentRefreshRate : 59​

CurrentScanMode : 4​

CurrentVerticalResolution : 1440​

Description : NVIDIA GeForce GTX 1660 SUPER​

DeviceID : VideoController1​

DeviceSpecificPens :​

DitherType : 0​

DriverDate : 20210506000000.000000-000​

DriverVersion : 27.21.14.6259​

ErrorCleared :​

ErrorDescription :​

ICMIntent :​

ICMMethod :​

InfFilename : oem7.inf​

InfSection : Section074​

InstallDate :​

InstalledDisplayDrivers : C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_d32078c1f36dc73e\nvld​

umdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_d32078c1f36d​

c73e\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_d32​

078c1f36dc73e\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_​

amd64_d32078c1f36dc73e\nvldumdx.dll​

LastErrorCode :​

MaxMemorySupported :​

MaxNumberControlled :​

MaxRefreshRate : 60​

MinRefreshRate : 29​

Monochrome : False​

Name : NVIDIA GeForce GTX 1660 SUPER​

NumberOfColorPlanes :​

NumberOfVideoPages :​

PNPDeviceID : PCI\VEN_10DE&DEV_21C4&SUBSYS_873C1043&REV_A1\4&1955A1F&0&0010​

PowerManagementCapabilities :​

PowerManagementSupported :​

ProtocolSupported :​

ReservedSystemPaletteEntries :​

SpecificationVersion :​

Status : OK​

StatusInfo :​

SystemCreationClassName : Win32_ComputerSystem​

SystemName : PHOBOS​

SystemPaletteEntries :​

TimeOfLastReset :​

VideoArchitecture : 5​

VideoMemoryType : 2​

VideoMode :​

VideoModeDescription : 2560 x 1440 x 4294967296 colors​

VideoProcessor : GeForce GTX 1660 SUPER​

PSComputerName : PHOBOS​

​

​

​

PS C:\Windows\system32>​

Still not pretty.

 

[Ancient Forester]

so basically the powershell "paste" of "Get-WmiObject win32_baseboard; Get-WmiObject Win32_Bios; Get-WmiObject win32_physicalmemory | Select Manufacturer,Banklabel,Configuredclockspeed,Devicelocator,Capacity,Serialnumber; Get-ComputerInfo OSName, OsArchitecture; Get-WmiObject win32_VideoController" into an admin powershell will give the information about the system (windowskey+x, powershell (admin), paste the string to get the objects out of device manager, copy the whole shebang from the window, paste. Leading with status about does it work or not. It ain't pretty but it gives the data. But before we start collecting, let's find out if they want the entire thing in a .txt file for machine reading. Time to get fdev involved in collecting this (They'll get a bunch of "this works", and "this don't" data to sift through to hopefully find the pattern I was arrogant enough to think I had found. I was wrong, time for someone better than me. )

 

[the100thmonkey]

True but why is the same code buggier on some machines than others?

There are some inconsistencies, sure, but if you look at the "what is an acceptable FPS?" thread, and in other communities, you'll find a great many people who are very tolerant of appalling performance for the hardware they run. A lot of people just don't care that much.

Edit

On-topic:

Ryzen 5 3600 with a PBO overclock - ~4.0GHz
16GB DDR4-3200 CL16 - 2x8GB DIMMs, bought as a pair.
RTX 2060 - vanilla, with a ~10% overclock
Asrock B450 Steel Legend
1TB Crucial NVME SSD

The game runs like hot garbage in Odyssey settlements at 1080p. At 720p, it runs much better - 60fps in stations with vsync, with dips into the 40s in Odyssey conflict zones. vRAM usage gets up to about 5,500MB in both stated areas at 720p. I'm yet to test at 1080p.

 

[Ancient Forester]

There are some inconsistencies, sure, but if you look at the "what is an acceptable FPS?" thread, and in other communities, you'll find a great many people who are very tolerant of appalling performance for the hardware they run.

This is very true, and what is an acceptable FPS for a game engine varies from game engine to game engine.

Luckily in our case, the developers have given us a great guideline of we press control+f on our keyboards to bring up the ingame fps counter. They've colorcoded it. Anything not green is ... less than ideal. Anything red should be considered in the unplayable range.

 

[devilronin]

The common denominator is buggy code.

maybe its windows 10?(im still on 7 for a while)

 

[Ancient Forester]

maybe its windows 10?(im still on 7 for a while)

It CAN be, but I sincerely doubt it. There are several players on Win10 who are running great working versions. It can however be a specific method of windows 10 installation (using a clean windows vs a manufacturer one, for instance)

 

[Mogen Teras]

Let's stop blaming hardware and call it as it is: bad software.

Let me tell you a story. I have 3090 RTX GPU and the game is freshly installed on M2 SSD. I set everything to high or ultra, rightfully so, and then toned down shadows a notch - as a graphics engineer I know they are taxing for little quality benefit.

The game struggles to keep 60 FPS. On a fastest GPU available on the planet, that has 24 GB video memory. There are hick-ups while streaming in. On M2 hooked up to CPU directly. All of this to produce image quality far below what recent games are able to produce with much higher framerates.

It's not hardware. It's simply bad software.

I'm tempted to run it through PIX to see what the hell they are doing.

This. Let's not try to pretend this anything but developer error.

 

[Ancient Forester]

Keep up the good work, I'm going to bed with a good book (it's 0311 in the morning here now). We can do this!

 

[Ancient Forester]

This. Let's not try to pretend this anything but developer error.

The only thing this contribution helps with is to serve as a vent. You are adding exactly zero useful information. In what way is it failing and on what hardware combination. Remember these are muggle developers, they never got their letter from Hogwarts, they never went to divination class and they can't use a crystal ball to see your pc specs.

 

[Cmdr Alphonso Dementia]

I forgot to mention that don‘t indulge in any pew-pew. I probably should try something like a simple personal data retrieval mission just to check out what happens in a settlement. I have just been using EDO the same way I use EDH, with just an occasional walk into the station to see if Sleepy Pete has escaped from his captors... So far, he’s still MIA.