Forums

Bestiary update

Quick find code: 294-295-155-64423836

E U H God X
Aug Member 2009

E U H God X

Posts: 50 Iron Posts by user Forum Profile RuneMetrics Profile
Would a graphics setting option be available? I'd like to be able to see the monsters in x4 AA, HD, minimum lighting detail... etcetera. Would this be applicable?

Another thing would be to allow camera controls a bit more like the current orb of oculus. We'd be able to see different angles, but this could be a different control setting.

A few more things would be fixes: Adding missing monsters such as the dagannoth kings, being able to see more animations from monsters, or putting in the options that should be there (such as shadow-forger ickziggybuggydoo: he only has idle and death).

Thanks!
Twisted and maniacal - a slathering testament to the powers of corruption!

19-Apr-2013 18:07:57

Dragoncrent

Dragoncrent

Posts: 1,647 Mithril Posts by user Forum Profile RuneMetrics Profile
I think the Bestiary needs another update. I just loaded it up perfectly fine with Firefox Aurora after modifying a few of the browser's settings, and got to use it for about two seconds just fine before it redirected me to a screen saying "Update to Google chrome!"

21-Apr-2013 17:54:36

Jedi Invoker

Jedi Invoker

Posts: 461 Silver Posts by user Forum Profile RuneMetrics Profile
This is a reminder for CM Team to pass this message along to the developers involved with Bestiary.

There was a problem with many people not being able to use Bestiary and it was the first Runescape website tool to use HTML5. After a long time, the problem still exists and it is a shame that it isn't fixed yet. Jagex decided to release RS3 client beta with this bug in it.

The issue was identified by beta testers of RS3 and fixed in the HTML5 beta client by the developers involved, and quickly patched up by Mod Cyphus as an outcome of the discussion here:

QFC 334-335-23-64905019
QFC 334-335-981-64914411

but the fix has still not been applied to the Bestiary which results in constant complaints of Bestiary not working for several people.

TLDR; replace the unsecure WebSocket connection ws:// calls in Bestiary networking code with secure WebSocket connections wss:// calls

ws:// does not work with a large chunk of end users due to various reasons as discussed in the threads above. It should be replaced with either wss:// with TLS or an alternative link should be provided to make it work.

The fix is simple enough to do as it took them one day to implement . When are we getting a Bestiary fix?

23-Apr-2013 03:36:17

Quick find code: 294-295-155-64423836 Back to Top