Jump to content

Viewer broke in the last radeon adrenaline update

KydronAegis

By KydronAegis,
in Second Life Viewer

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

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

Recommended Posts

KydronAegis

KydronAegis

Posted
Posted

Grettings everyone! I need a bit of help here

 

I'm a AMD user, and I updated my radeon adrenaline software for the last update (23.4.3) to play other stuff, but when I tried to use SL/Firestorm, the viewer simply broke, not even reinstall helps to solve that problem....

 

 

what shoud I do? rollback? wait for a update? give up?

 

I would be grateful if someone could help me in this problem ^^ thanks!

Link to comment
Share on other sites
Kathrine Jansma

Kathrine Jansma

Posted
Posted
13 hours ago, KydronAegis said:

the viewer simply broke

Define "broke". That could be anything.

What does not work anymore?

Does the viewer crash on startup?

Does it just look bad?

 

I use the Cool VL Viewer, Firestorm, Genesis and 23.4.3 with a Vega 56 and it still works as good or bad as with most previous drivers. 

If you suspect the driver being the culprit, rolling back to a known good driver might be a good idea.

Link to comment
Share on other sites
Rowan Amore

Rowan Amore

Posted
Posted
40 minutes ago, KydronAegis said:

oh, sorry for the lack of description

 

the game just crash, sometimes it runs for just 30 seconds, and crashes

 

with every viewer I tested, this happend

It would be helpful if you posted your computer stats from the viewer   Help/About at the top menu in the viewer, then copy to clipboard and paste here.

Link to comment
Share on other sites
KydronAegis

KydronAegis

Posted
  • Author
Posted
1 hour ago, Rowan Amore said:

It would be helpful if you posted your computer stats from the viewer   Help/About at the top menu in the viewer, then copy to clipboard and paste here.

Firestorm 6.6.8 (68380) Jan  3 2023 19:59:43 (64bit / SSE2) (Firestorm-Releasex64) with Havok support
Release Notes

CPU: AMD Ryzen 5 5600G with Radeon Graphics          (3900 MHz)
Memory: 15664 MB
Concurrency: 12
OS Version: Microsoft Windows 10 64-bit (Build 19045.2965)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: AMD Radeon(TM) Graphics
Graphics Card Memory: 8087 MB

Windows Graphics Driver Version: 31.0.14051.5006
OpenGL Version: 4.6.0 Compatibility Profile Context 23.4.3.230420

RestrainedLove API: (disabled)
libcurl Version: libcurl/7.54.1 OpenSSL/1.1.1l zlib/1.2.11.zlib-ng nghttp2/1.40.0
J2C Decoder Version: KDU v8.2
Audio Driver Version: FMOD Studio 2.02.09
Dullahan: 1.12.4.202209142021
  CEF: 91.1.21+g9dd45fe+chromium-91.0.4472.114
  Chromium: 91.0.4472.114
LibVLC Version: 3.0.16
Voice Server Version: Not Connected
Settings mode: Firestorm
Viewer Skin: Firestorm (Grey)
Window size: 1440x837 px
Font Used: Deja Vu (96 dpi)
Font Size Adjustment: 0 pt
UI Scaling: 1
Draw distance: 96 m
Bandwidth: 2500 kbit/s
LOD factor: 2
Render quality: Medium-Low (2/7)
Advanced Lighting Model: No
Texture memory: Dynamic (512 MB min / 10% Cache / 10% VRAM)
Disk cache: Max size 2048.0 MB (100.0% used)
Built with MSVC version 1934
May 21 2023 09:09:19 SLT

Link to comment
Share on other sites
Rowan Amore

Rowan Amore

Posted
Posted
1 hour ago, Coffee Pancake said:

try the official viewer

 

1 minute ago, davidventer said:

Don't let the FS cult see you make such a suggestion, they'll come for you with burning pitchforks. But yeah, great suggestion!

They did say with every viewer they tried, the same.thing happened.

  • Like 1
Link to comment
Share on other sites
Coffee Pancake

Coffee Pancake

Posted
Posted
4 hours ago, Rowan Amore said:

 

They did say with every viewer they tried, the same.thing happened.

The Linden viewer is can be several months of development ahead of firestorm, all viewers are in very large part based entirely on Linden code.

It is always worth testing against regardless of how many third party viewers have already been tried, honestly I wish this what what people tried first and you wouldn't believe how hard it can be to get people to actually do it sometimes.

Just knowing the problem has already been solved by LL saves an insane amount of support and developer time.

  • Like 2
Link to comment
Share on other sites
KydronAegis

KydronAegis

Posted
  • Author
Posted
1 hour ago, Coffee Pancake said:

The Linden viewer is can be several months of development ahead of firestorm, all viewers are in very large part based entirely on Linden code.

It is always worth testing against regardless of how many third party viewers have already been tried, honestly I wish this what what people tried first and you wouldn't believe how hard it can be to get people to actually do it sometimes.

Just knowing the problem has already been solved by LL saves an insane amount of support and developer time.

well, like I said before, I tested, the oficial viewer, firestorm and black dragon

 

I got the same result for all those tests, the viewer opens, but immediately when something appears, it crashes and I got a bug report message.

Link to comment
Share on other sites
Rowan Amore

Rowan Amore

Posted
Posted
5 minutes ago, KydronAegis said:

well, like I said before, I tested, the oficial viewer, firestorm and black dragon

 

I got the same result for all those tests, the viewer opens, but immediately when something appears, it crashes and I got a bug report message.

If the viewers worked before you updated the drivers, go ahead and roll them back as mentioned.  There have been issues before with driver updates and SL.

Link to comment
Share on other sites
Theresa Tennyson

Theresa Tennyson

Posted
Posted
15 hours ago, KydronAegis said:

Firestorm 6.6.8 (68380) Jan  3 2023 19:59:43 (64bit / SSE2) (Firestorm-Releasex64) with Havok support
Release Notes

CPU: AMD Ryzen 5 5600G with Radeon Graphics          (3900 MHz)
Memory: 15664 MB
Concurrency: 12
OS Version: Microsoft Windows 10 64-bit (Build 19045.2965)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: AMD Radeon(TM) Graphics
Graphics Card Memory: 8087 MB

Windows Graphics Driver Version: 31.0.14051.5006
OpenGL Version: 4.6.0 Compatibility Profile Context 23.4.3.230420

RestrainedLove API: (disabled)
libcurl Version: libcurl/7.54.1 OpenSSL/1.1.1l zlib/1.2.11.zlib-ng nghttp2/1.40.0
J2C Decoder Version: KDU v8.2
Audio Driver Version: FMOD Studio 2.02.09
Dullahan: 1.12.4.202209142021
  CEF: 91.1.21+g9dd45fe+chromium-91.0.4472.114
  Chromium: 91.0.4472.114
LibVLC Version: 3.0.16
Voice Server Version: Not Connected
Settings mode: Firestorm
Viewer Skin: Firestorm (Grey)
Window size: 1440x837 px
Font Used: Deja Vu (96 dpi)
Font Size Adjustment: 0 pt
UI Scaling: 1
Draw distance: 96 m
Bandwidth: 2500 kbit/s
LOD factor: 2
Render quality: Medium-Low (2/7)
Advanced Lighting Model: No
Texture memory: Dynamic (512 MB min / 10% Cache / 10% VRAM)
Disk cache: Max size 2048.0 MB (100.0% used)
Built with MSVC version 1934
May 21 2023 09:09:19 SLT

Try turning advanced lighting on - you don't have to turn on shadows. The non-advanced lighting rendering engine is pretty old and may no longer be compatible with the new drivers.

  • Like 1
Link to comment
Share on other sites
Resi Pfeffer

Resi Pfeffer

Posted
Posted

I sadly dont have any solution for this issue, as i suffer from another one myself

@Wulfie Reanimator
Like you mentioned above, I do get logged out by force constantly when crossing sims (sailing, flying), and i get the respective message "you've been disconnected from second life"
It happens mostly after 5-20 sim crossings. Im crossing the border into the next region (pretty smooth), loose all control, keep sliding over the whole region and then i hit an invisible wall. After 30 seconds i get logged out.
Very often i also see regions around me turning red for a few seconds on the minimap and then back to normal, before i make the next crossing where i finally will die, while others dont have an issue at all.
Im not aware of having changed anything since half a year, where the issues started suddenly. im connected with a cable to my router, my packet loss is 0, ive tried with an alt and experienced the same problem, switched between 3 different mesh bodies, even used the system avatar, clean FS reinstall, etc.

What i didnt try yet is what was mentioned above by someone... leaving ALM on. 

Any other ideas, maybe? :)

Link to comment
Share on other sites
Gavin Hird

Gavin Hird

Posted
Posted
On 5/31/2023 at 6:23 AM, KydronAegis said:

Soo, I did a rollback for a older version of the amd software, the viewer still broke

 

 

I kinda give up for now lol

But if I understand your messages right, my viewer still works for you both before and after the rollback?

Link to comment
Share on other sites
KydronAegis

KydronAegis

Posted
  • Author
Posted
On 6/1/2023 at 3:12 AM, Gavin Hird said:

But if I understand your messages right, my viewer still works for you both before and after the rollback?

Only yours, yeah

 

 

for some reason, the other ones just close when the world loads

  • Like 1
Link to comment
Share on other sites
You are about to reply to a thread that has been inactive for 365 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
Go to topic listing
×
×
  • Create New...