Jump to content

64 bit Viewers black background vs 32 bit work great


You are about to reply to a thread that has been inactive for 928 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Looking for some understanding of the difference I am experiencing between the 64 and 32 bit viewers today.

 

Starting yesterday I have been running a 64 bit gamers pc, fresh reset of Windows 10. I installed FS 64 bit early on, and was astounded with super performance and consistent fps upwards to 190.  Over many restarts and power ups all days long, I ran FS again and again, and worked it hard, with the same results. Really happy.

I powered up and ran that same FS 64 this morning to a perpetual black background.  I could mouseclick in the form fields for username and password, it moved the cursor forward when I typed, and I could tab to the password field and it moved the cursor as I typed there.  But I cannot tell if any text was really registering (black bkgd/black font presumed). 

>> I uninstalled FS 64 and installed SL Viewer with the same experience.

>> I uninstalled SL viewer, installed FS 32 bit, and it works great - but fewer fps. 

 

What could cause such a difference in one day, where 64 bit viewer works stellar, then wont even allow me to login on both FS and SL 64 bits?

And why would the 32 bit FS then work today, when at the same time the 64 bit FS and SL won't?

 

All the guesses I have for why seem to be refuted in almost 15 hours of stellar performance yesterday.  We could talk about parts/resources and such, but 15 hours of hard labor and many restarts and power down/ups yesterday suggests the parts work together fine under a good deal of use.  

Appreciate any thoughts on what the difference is.  

Link to comment
Share on other sites

Sounds like a discrepancy between the graphics used by your computer and settings in FS or FS identifies graphic system wrongly.

Either way, best answers only possible if we know your system, in FS go to Help->About Firestorm->Copy to Clipboard. Paste the content here.

 

Link to comment
Share on other sites

The 64 bit remains the same this morning, where the background orange fails to load/no login.  The 32 bit FS which works well, on Windows 10 Home. This pc has Intel and Nvidia, and in Windows 10 settings I have assigned the fs .EXE to use High Performance/Nvidia, and depending on window size I am getting between 70-170 fps today so the 32 bit (below) I am happy with.  

 

Firestorm 6.3.2 (58052) Sep 28 2019 09:08:31 (32bit) (Firestorm-Release) with Havok support
Release Notes

You are at 206.9, 25.1, 4,072.9 in Chillium located at sim10439.agni.lindenlab.com (216.82.51.145:13014)
SLURL: http://maps.secondlife.com/secondlife/Chillium/207/25/4073
(global coordinates 298,191.0, 278,041.0, 4,072.9)
Second Life Server 2020-03-09T23:50:45.538236
Release Notes

CPU: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (3696 MHz)
Memory: 16243 MB
OS Version: Microsoft Windows 8 64-bit (Build 9200)
Graphics Card Vendor: Intel
Graphics Card: Intel(R) UHD Graphics 630

Windows Graphics Driver Version: 26.21.14.4250
OpenGL Version: 4.2.0 - Build 26.20.100.7262

RestrainedLove API: (disabled)
libcurl Version: libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.8 nghttp2/1.25.0
J2C Decoder Version: KDU v7.10.7
Audio Driver Version: FMOD Studio 2.00.03
Dullahan: 1.1.1320 / CEF: 3.3626.1895.g7001d56 / Chromium: 72.0.3626.121
LibVLC Version: 2.2.8
Voice Server Version: Not Connected
Settings mode: Firestorm
Viewer Skin: StarLight CUI (Custom Light)
Window size: 1846x1012 px
Font Used: Deja Vu (96 dpi)
Font Size Adjustment: 0 pt
UI Scaling: 1
Draw distance: 32 m
Bandwidth: 1000 kbit/s
LOD factor: 2
Render quality: Medium-Low (2/7)
Advanced Lighting Model: No
Texture memory: 512 MB (1)
VFS (cache) creation time (UTC): unknown
Built with MSVC version 1800
Packets Lost: 10/299,109 (0.0%)
March 19 2020 12:36:08 SLT

Link to comment
Share on other sites

HI W, and thanks for replying.

Knowing we have a mix of pros and hobbiest folks in this audience, I can see how you might believe a hobbiest might have missed in the info above "Windows 8" after I said I was running Win10.  I would not be on the hobbiest side.  To me, and you, that stood out naturally.  If you knew me, you'd know when I shared that I was running Windows 10 Home, I live the dream for sure.  I saw above too in the Firestorm info, and knowing the facts as I live them, it appears something in FS or Windows 10 is sending/receiving wrong OS info to my 32 bit FS.  And if any question, officially yes, this is a "gamers pc".  

Windows 10

 

EDIT ADD gpu screencap, is set to Nvidia. When set to Nvidia instead of default Intel, fps went heavenly: 

GPU set High Priority/Nvidia

 

Thanks for trying. Respectful responses always appreciated,  And there may be no answer, which is fine. But many of us love riddles.  Here it seems likely the issue when it is identified will be much more interesting than OS identity in the info.  🙂

Edited by Kyrie Deka
Link to comment
Share on other sites

5 hours ago, Wulfie Reanimator said:

Your "gamer PC" doesn't seem to have a dedicated GPU, and is running on Windows 8, not 10.

32bit viewers don't set Windows 10 compatibility to allow people with older Intel HD2000/3000 GPUs to be still able to use Second Life, which results in Windows identifying itself to those viewers as Windows 8.

Apart from that, I would check the dual GPU settings in the nVidia command center instead of that Windows settings thingy. I wouldn't trust that any inch. ;)

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

2 hours ago, Ansariel Hiller said:

check the dual GPU settings in the nVidia command center instead of that Windows settings thingy. I wouldn't trust that any inch. ;)

Thanks!  I ran and did that.  I looked in Apps in Nvidia, then I also went to the Nvidia Control Center which looks a little different.

The 32 bit FS remains usable, though I hit a max after a few hours of memory and have to relog. But its livable and fast.  No noticeable difference setting the EXE inside Nvidia, and Info still shows Intel.  Although if the Windows 8 was designed to show that way in info, perhaps Intel showing there is/not necessarily telling also?

The 64 bit FS, added to Nvidia, but remains the same black bkgd (specifically, the orange graphics/no graphics/nothing but black black black show anywhere).  Oddly enough, I just tried to logon, I can tell where the username pswd boxes and tab to Home - am I logged in?  Maybeeee - I just cannot tell because just about everything is black.  Not sure what those bars are.  

64 bit where I may/not be logged in

So-on the same pc, same settings, same Nvidia app settings for both EXE files, Win 10 settings that I am aware of, same antivirus settings, same conditions otherwise seemingly - what could cause that [overlay??] over the 64 bit version, but not have the [overlay?] when starting and running the 32 bit version?

Watch it be something silly, like I didn't dot-an-eye or cross a tee :))) - though that would be good news to know what it is.

Link to comment
Share on other sites

 

962504472_NVIDIAControlPanel.thumb.png.0cfebbce12eed74767d1682cf07ab8b7.png

Open the NVIDEA Control Panel and set GPU to use your GForce.

Set Power management mode to Prefer maximum performance

Be sure to click Apply, reboot your system and see, if above solves your problem. But I fear, if system is identified as Windows 8 by Firestorm and you have Windows 10 the problems are deeper.

 

Edited by Rachel1206
Link to comment
Share on other sites

On 3/21/2020 at 8:37 AM, Rachel1206 said:

the NVIDEA Control Panel and set GPU to use your GForce.

Set Power management mode to Prefer maximum performance

Hiya and thanks for sharing!  I believe those were already set that way in global, but I ran and made sure all was as you shared, rebooted, and the issue continues.  Its a conundrum.  Bug report submitted. Thanks all!

  • Thanks 1
Link to comment
Share on other sites

  • 2 weeks later...
  • 7 months later...
On 3/19/2020 at 3:58 PM, Kyrie Deka said:

The 64 bit remains the same this morning, where the background orange fails to load/no login.  The 32 bit FS which works well, on Windows 10 Home. This pc has Intel and Nvidia, and in Windows 10 settings I have assigned the fs .EXE to use High Performance/Nvidia, and depending on window size I am getting between 70-170 fps today so the 32 bit (below) I am happy with.  

 

Firestorm 6.3.2 (58052) Sep 28 2019 09:08:31 (32bit) (Firestorm-Release) with Havok support
Release Notes

You are at 206.9, 25.1, 4,072.9 in Chillium located at sim10439.agni.lindenlab.com (216.82.51.145:13014)
SLURL: http://maps.secondlife.com/secondlife/Chillium/207/25/4073
(global coordinates 298,191.0, 278,041.0, 4,072.9)
Second Life Server 2020-03-09T23:50:45.538236
Release Notes

CPU: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (3696 MHz)
Memory: 16243 MB
OS Version: Microsoft Windows 8 64-bit (Build 9200)
Graphics Card Vendor: Intel
Graphics Card: Intel(R) UHD Graphics 630

Windows Graphics Driver Version: 26.21.14.4250
OpenGL Version: 4.2.0 - Build 26.20.100.7262

RestrainedLove API: (disabled)
libcurl Version: libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.8 nghttp2/1.25.0
J2C Decoder Version: KDU v7.10.7
Audio Driver Version: FMOD Studio 2.00.03
Dullahan: 1.1.1320 / CEF: 3.3626.1895.g7001d56 / Chromium: 72.0.3626.121
LibVLC Version: 2.2.8
Voice Server Version: Not Connected
Settings mode: Firestorm
Viewer Skin: StarLight CUI (Custom Light)
Window size: 1846x1012 px
Font Used: Deja Vu (96 dpi)
Font Size Adjustment: 0 pt
UI Scaling: 1
Draw distance: 32 m
Bandwidth: 1000 kbit/s
LOD factor: 2
Render quality: Medium-Low (2/7)
Advanced Lighting Model: No
Texture memory: 512 MB (1)
VFS (cache) creation time (UTC): unknown
Built with MSVC version 1800
Packets Lost: 10/299,109 (0.0%)
March 19 2020 12:36:08 SLT

I had the same thing happen in June. I dropped to 32 and ran fine. After using it for a week or so, I attempted 64 again and was okay. This situation is odd in that this time the screen doesn't even load at all. After "initializing" it appears to go back to the icon on the desktop. And what I find odd is that the SL viewer does the exact same thing.

 

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 928 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...