Information regarding 2008-era NVIDIA GPU issues

Blazer Nitrox
Guest

Information regarding 2008-era NVIDIA GPU issues Sept 1, 2017 21:36:59 GMT apophys and RiftandRend like this

Quote

Post by Blazer Nitrox on Sept 1, 2017 21:36:59 GMT

Good day, everybody.

I am creating this thread because I, too, have stumbled across the "2008-erase GPUs not working" issue.

After doing some research, it seems that everyone who has stumbled across this issue has a Tesla-based NVIDIA graphics card.

Evidence:
paleblackdot reports:

Each button click takes me 3-5 minutes of loading time to move on (if it let's me move on at all). So far, I've been unable to get past the first menu after clicking on the campaign button before it seems like it stops entirely

My system specs are:

Windows 7 Home Premium, SP1
Intel Core I7 CPU, 2.67 GHz
9.00 GB RAM
64 bit OS
Nvidia GeForce GTX 260

subyng also reports:

Update: turns out the game is running REALLY REALLY slowly, but it does respond. Takes several seconds before anything happens when I click a button. I managed to get into a mission, and again, everything is unresponsive; the framerate is effectively less than 1.

Windows 7 64-bit
i5-4690 3.50Ghz
8 GB Ram
GeForce 9800 GT

As well as myself:

The game seems to have an extreme amount of lag at all of the menus. I haven't even managed to get into the game itself yet because clicking on any of the buttons results in a 2-3 minute wait. I have managed to get into the Options menu, and I have turned all of the settings down as far as I can. The C/GPU aren't doing much, and it isn't accessing anything from the hard drive.

My specs:
Windows 7 64-bit
i7 920XM @ 2.0 GHz (2.2 boost)
NVIDIA Quadro FX 2800M
16GB RAM

My settings (taken from %userprofile%\AppData\Roaming\CDE\Preferences.txt):

Preferences MainOptions
Interface
	GameTheme						Default
	VerboseTooltips					false
	InvertMouseRotation				false
	ShowCelestialGridWhenRotating	false
	LockCameraToPlane				false
	ProjectOrbitsOnToSelectedPlane	false
	ProjectTrajectoryOnToReferenceFrame	false
	ShowLagrangePoints				false
	UseMouseDragForThrustManipulation	false
	UseMultiaxialThrustManipulation	false
Gameplay
	PauseCombatAtStart				false
	ShowCombatNotifications			false
	ShipsMarqueeSelect				false
	ModuleAdvancedOptionsOpen		false
Audio
	MasterVolume_Percent			1
	MusicVolume_Percent				1
	InterfaceVolume_Percent			1
	EffectsVolume_Percent			1
Graphics
	Fullscreen						false
	ScreenScaling_Percent			0.5
	VSync							false
	Brightness_Percent				1
	FieldOfView_degrees				50
	Textures
		ArmorTextureQuality			Low
		ParallaxOcclusionMapQuality	Low
		TextureSelfShadowingQuality	Low
	Lighting
		ShadowMapQuality			Low
		RadiatorLighting			false
		BounceLighting				false
	PostProcessing
		Antialiasing				false
		BloomAmount					0
		DrawDiffractionSpikes		false
		RenderDiffractionShimmer	false
	DisableCustomCursor				false

What all of these have in common is

Abysmal performance to the point where menu items take minutes to respond
Changing the settings in either the game or the preference file has no effect on performance
The GPUs in question are all based on the Tesla architecture

I have also tried forcing the game to use my (totally garbage) integrated graphics, but the NVIDIA control panel provides no way to do this (the best I could do was allow it to auto-select, which always resulted in it using the graphics card anyway).

I do not know what it is about Tesla that is causing this issue, but it may be related to the fact that the drivers for this architecture only support up to OpenGL 3.2 and DirectX 10, and have no support whatsoever for Vulkan.

Whatever the issue is, I (and several others, by the looks of things) would be extremely happy to see something done about this. I am in school currently, but I am usually available between 5 and 10 Pacific Time, and would be perfectly willing to help in any way I can.

Blazer Nitrox
Guest

Information regarding 2008-era NVIDIA GPU issues Sept 3, 2017 18:32:40 GMT

Quote

Post by Blazer Nitrox on Sept 3, 2017 18:32:40 GMT

I'm putting this here in case there are other people who completely missed this fact:
CDE uses OpenGL and NOT DirectX. This explains why modern NVIDIA GPUs (Pascal, for one) are having issues, since apparently a recent driver update completely broke OpenGL support. I suspect that CDE may be using a version of OpenGL newer than 3.2, which would also explain the problems Tesla-based cards are having (although why it is just running terribly and not crashing outright isn't explained).

jtyotjotjipaefvj
Senior Member

Posts: 448

Information regarding 2008-era NVIDIA GPU issues Sept 3, 2017 19:07:39 GMT

Quote

Post by jtyotjotjipaefvj on Sept 3, 2017 19:07:39 GMT

Sept 3, 2017 18:32:40 GMT Blazer Nitrox said:

since apparently a recent driver update completely broke OpenGL support.

This is blatantly false. CoaDE works fine on my GTX 1080, and all OpenGL applications I've made myself work fine too.

Edit: it can't be CoaDE using a newer OpenGL version than supported either. Window creation would fail and the game would crash on startup if that was the case.

Last Edit: Sept 3, 2017 19:14:22 GMT by jtyotjotjipaefvj

Blazer Nitrox
Guest

Information regarding 2008-era NVIDIA GPU issues Sept 3, 2017 21:26:56 GMT

Quote

Post by Blazer Nitrox on Sept 3, 2017 21:26:56 GMT

Sept 3, 2017 19:07:39 GMT jtyotjotjipaefvj said:

This is blatantly false. CoaDE works fine on my GTX 1080, and all OpenGL applications I've made myself work fine too.

First: I'm sorry I didn't make myself as clear as I would have liked. What I meant was that there were many, many reports of driver version 378.49 breaking OpenGL in several games, and I am still hearing reports of this issue persisting clear up to the current driver (385.41 as of this writing).

I should also point out that your particular rig may be an anomaly (you may not have issues, but someone else may). One should also consider the fact that even if your card is having issues with the game, it's so bloody powerful (a GTX 1080 as compared to the recommended Intel HD 4000) that it may be able to just brute force its way through the problem.

Second:

Sept 3, 2017 18:32:40 GMT Blazer Nitrox said:

I suspect that CDE may be using a version of OpenGL newer than 3.2, which would also explain the problems Tesla-based cards are having (although why it is just running terribly and not crashing outright isn't explained).

jtyotjotjipaefvj
Senior Member

Posts: 448

Information regarding 2008-era NVIDIA GPU issues Sept 3, 2017 22:24:45 GMT

Quote

Post by jtyotjotjipaefvj on Sept 3, 2017 22:24:45 GMT

That driver issue must not be affecting CoaDE anymore at least, I've been running 385.41 for a while now and haven't run into any more crashes than usual.

I also highly doubt that a 1080 would be fast enough to deal with loads that take minutes to render on other pascal cards. The difference between a 1050 and a 1080 is a 2-3x improvement in performance, not thousands of times as it would have to be.

Blazer Nitrox
Guest

Information regarding 2008-era NVIDIA GPU issues Sept 4, 2017 1:12:27 GMT

Quote

Post by Blazer Nitrox on Sept 4, 2017 1:12:27 GMT

You make a valid point about brute-forcing the performance, but otherwise I feel we have strayed from the topic at hand, which is that Tesla-based cards seem to have a mysterious issue with CoaDE.

Would you happen to know how CoaDE addresses OpenGL (i.e. does it talk directly to OpenGL or does it go through a library such as SDL)?