• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

NVIDIA GeForce RTX 50 Series Faces Compute Performance Issues Due to Dropped 32-bit Support

Nvidia is just following Apple, Apple always provide past architecture support to their customer but only to a degree and deprecate relatively abruptly (reading this cuda 32bit story, Mac OSX Lion drop of support for pre Intel code came to mind).
That was the big difference with Microsoft that tend to keep support for much longer, not caring much about bloating their soft, but even them seem to have change and start taking a similar approach.
I would argue that, developing and releasing a translation layer to keep those old codes running would be a more cavalier approach. But this cost money for no real return and considering the un-charity level of big US corp today, this is a max-level pipe dream at this point...
 
Even though Nvidia had said it planned to end support for 32-bit CUDA apps, they should have clearly stated which version will be pilot in this case. AMD does not support OpenCL software-wise for years either, but hardware-wise still does. So Nvidia dropped even hardware support now.

Those who think that OpenCL is not being used anymore, ask all cryptominers.

As for Passmark software, it's piece of shit software and this has been known for years. I'd compare Passmark to GeekBench in terms of amplitude of "shitness".

Anyway, those who need 32-bit CUDA support can go for RTX 4000 series. They are no worse than RTX 5000 series, you really don't need MFG support for older games that rely on PhysX.

I agree with @Assimilator on that Nvidia should have made some workaround (transition layer) available to retain backward compatibility.

So, Nvidia invested all time, money and effort to AI stuff, dropped support for anything no longer related, thus minimizing costs for gamers hardware and maximizing for one for AI. Which tells no other story but that one in which Nvidia does not give a f*ck about gamers anymore.

And where does this all lead to? For those who can't clearly see, Nvidia aims to provide small ARM-based boxes, more like terminals, for users to connect to their GeForce NOW cloud computing service for playing games. Monthly fee included. Something like Xbox Pass with streamed games instead of rendered locally. People are more and more staggering to afford new GPUs, prices are insane. This will be Nvidia's response: get this small cheap box, you've got 6 months of membership fee included, then you pay monthly fee, so we can keep it raising and you won't be able to do anything about it since we no longer make gaming GPUs.
 
By far, those are not only THE WORST video cards released by nVidia, but also THE WORST generation of video cards ever released by this company.
It's not even a contest.
And suckers are still buying this overpriced junk. Unbelievable is the human stupidity...
 
Did you miss my post showing that AMD dropped support after 2015?

I've read your message and here is my follow up: No it does Not.

AMD is a very interesting corporation. I worked for it, it was a contract, and I know that inside AMD a "right hand" does Not know what a "left hand" is doing. So, if some webpage is Not updated it does Not mean that support is completely removed.

OpenCL is still supported by AMD and, if you use an AMD GPU card, you can check the latest version of OpenCL driver installed on your computer.

There are two simple ways:

1. Execute clinfo.exe utility and check all details for AMD Platform and AMD OpenCL device ( It is your GPU or a CPU / Take into account that OpenCL supports GPU-type and CPU-type devices )

2. In ..\Windows\System32 folder find two DLLs, amdocl.dll and amdocl12cl.dll, and check versions: Select a DLL -> Right click -> Properties -> Details -> All information about the DLL will be displayed

Here is a screenshot for amdocl.dll:

AmdOclDllInfo.jpg


Here is a screenshot for amdocl12cl.dll:

AmdOcl12clDllInfo.jpg
 
Last edited:
Is it so hard for nvidia to just leave 32-bit CUDA stuff in the state it is and attach it to the current driver and fix bugs from time to time if any are found because of many of software requiring it? I don't think so. They just want you locked in the upgrade conveyor that leads to nowhere and more "riches" for the "rich".
 
Last edited:
Is it so hard for nvidiots to just leave 32-bit CUDA stuff in the state it is and attach it to the current driver and fix bugs from time to time if any are found because of many of software requiring it? I don't think so. They just want you locked in the upgrade conveyor that leads to nowhere and more "riches" for the "rich".

>>...Is it so hard for ... to just leave 32-bit CUDA stuff in the state it is...

If somebody has NVIDIA-OpenCL-32-bit problems take a look at how OpenCL is configured ( 32-bit and 64-bit ) on my primary development notebook. Two screenshots are inserted.

In overall, three OpenCL Platforms installed: AMD, Intel, and NVIDIA. Here are some technical details:

Number of platforms: 3

Platform Profile: FULL_PROFILE
Platform Version: OpenCL 1.2
Platform Name: Intel(R) OpenCL
Platform Vendor: Intel(R) Corporation
Platform Extensions: cl_intel_dx9_media_sharing cl_khr_byte_addressable_store cl_khr_d3d11_sharing cl_khr_dx9_media_sharing...

Platform Profile: FULL_PROFILE
Platform Version: OpenCL 2.1 AMD-APP ( 2580.6 )
Platform Name: AMD Accelerated Parallel Processing
Platform Vendor: Advanced Micro Devices, Inc.
Platform Extensions: cl_khr_icd cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_amd_event_callback...

Platform Profile: FULL_PROFILE
Platform Version: OpenCL 1.2 CUDA 10.1.321
Platform Name: NVIDIA CUDA
Platform Vendor: NVIDIA Corporation
Platform Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics...

64-bit OpenCL configuration

Nvidia64bitEnv.jpg


32-bit OpenCL configuration

Nvidia32bitEnv.jpg
 
quote tech article: This architectural change wasn't clearly documented by NVIDIA, whose developer website continues to display 32-bit code samples and documentation despite the removal of actual support.

I think I read recently that cuda32 is for 7 years already obsolete.

What about PhysX on old games that run 32bit code? I want to be able to play old games. Some of them are not even that old, like Batman.
 
What about PhysX on old games that run 32bit code? I want to be able to play old games. Some of them are not even that old, like Batman.

Here are steps I would complete for verification:

1. GPU-Z Utility

2. Find an installation package of your NVIDIA driver on NVIDIA Driver website -> Find Release Notes -> Check if PhysX is still supported

3. NVIDIA Control Panel should provide information

4. Verify if ..\Program Files (x86)\NVIDIA Corporation\PhysX folder exists
Here is a content of Common sub-folder:
...
Directory of C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common
28/03/2018 03:37 PM <DIR> .
28/03/2018 03:37 PM <DIR> ..
04/09/2016 03:35 PM 254,200 cudart32_65.dll
04/09/2016 03:35 PM 311,544 cudart64_65.dll
04/09/2016 03:35 PM 625,400 PhysXDevice.dll
04/09/2016 03:35 PM 675,064 PhysXDevice64.dll
04/09/2016 03:35 PM 57,592 PhysXLoader.dll
04/09/2016 03:35 PM 65,784 PhysXLoader64.dll
04/09/2016 03:35 PM 73,976 PhysXUpdateLoader.dll
04/09/2016 03:35 PM 90,872 PhysXUpdateLoader64.dll
...
 
What about PhysX on old games that run 32bit code? I want to be able to play old games. Some of them are not even that old, like Batman.

You have a 2080. You aren’t affected.
 
As I already stated some memory related params for 32-bit and 64-bit OpenCL drivers are different.

Just completed a quick verification for an OpenCL CPU-type device and here are results.

// 32-bit OpenCL test for a CPU-type device
...
Platform Name: Intel(R) OpenCL
Device Properties:
Profile : FULL_PROFILE
Version : OpenCL 1.2 (Build 76427)
Name : Intel(R) Core(TM) i7-xxxxXM CPU @ 3.00GHz
Vendor : Intel(R) Corporation
CL_DEVICE_MAX_COMPUTE_UNITS : 8
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1073709056 bytes
CL_DEVICE_GLOBAL_MEM_SIZE : 4294836224 bytes
CL_DEVICE_LOCAL_MEM_SIZE : 32768 bytes
...

// 64-bit OpenCL test for a CPU-type device
...
Platform Name: Intel(R) OpenCL
Device Properties:
Profile : FULL_PROFILE
Version : OpenCL 1.2 (Build 76427)
Name : Intel(R) Core(TM) i7-xxxxXM CPU @ 3.00GHz
Vendor : Intel(R) Corporation
CL_DEVICE_MAX_COMPUTE_UNITS : 8
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 8564342784 bytes
CL_DEVICE_GLOBAL_MEM_SIZE : 34257371136 bytes
CL_DEVICE_LOCAL_MEM_SIZE : 32768 bytes
...
 
Back
Top