Second Dreaming Part One - Testing & Bug Reports! Options

[Cironir]

Hello!

Please first read the "Test and Win" announcement on the blog first!

This thread is for REPORTING BUGS! Unsure how to report bugs? Read the detailed instructions!

Download the current test client here!

Important: The file includes a self-contained folder with a full Furcadia installation. Please put the folder somewhere on your computer, but make sure it is outside of the Program Files or Program Files (x86) folders. DO NOT overwrite your current Furcadia installation! The test version is completely independent of your regular Furcadia. After running furcadia.exe, you'll need to log in with your Furcadia account (CMS/web account). You can be logged into both worlds, the Live World and the Second Dreaming World. More information on how to install the test client can be found here!

The main focus of this testing phase is to test your dreams!
But please make backups of any dreams you upload or modify in the new editor. There will be another test version after this one.

[Cironir]

Known Issues (Please check here first!)
Note: This list is not exhaustive!

1. Help! I'm getting scrambled pixels in Live World!
   1. This is a known issue which occurs if you open Settings for the test client and click OK or Apply. It's actually a bug in the standard client where it picks up settings intended for the new client; the MissingNo-like scrambled pixels you see are what happens when the old code tries to load 32-bit FOX files!
   2. You can still play on both worlds without issue; just beware of the fact that if you use the test client's settings, then any alts you have open on the regular server will have corrupted graphics until you log out and back in. (No need to clear your cache - just close the window and log back in.)
2. Pounce keeps saying my friend is logging in and out over and over!
   1. This is a known issue which only occurs with test clients, but fortunately won't happen when we update! If you'd like, you can exit out of Pounce to stop it from doing that.

1. Whenever I join, summon, or click links I get spammed!
   1. Update to RC10 -- this issue has been fixed.
   2. This is a known issue that will disappear when we actually update. It happens in test builds because of Windows security measures.
   3. Normally, you give permission to run the Furcadia installer and this means Windows considers all of the installed Furcadia EXEs to be 'safe'. In a test build, there is no installer, so both the Furcadia client and the WinOpen EXE (which it uses to open links) have separate security prompts.
   4. You may be able to stop it from occurring by right-clicking on the WinOpen file in the Furcadia folder, selecting Properties and then clicking Unblock on the window that comes up.

This post has been edited by Treeki: Jul 22 2016, 11:47 PM

[Kye]

Not sure if it's a glitch or a cache error, but in the test world when I turn into a `kitsune, it just turns me into a rodent. :o

[Honesty]

When you upload your dream, and you have your own skin. I have the buttons listed as remap able but they are not showing as remapping colors.

Bug

Bug Title: Skin buttons not remap when you list them as remap
Character name: Honesty
Web Browser: Explorer
Furcadia test version: 31.0 RC8
Operating System: Windows 10
Details of the Bug: Skin Buttons listed as remap - not showing as remap
How can we make this bug happen again? - Upload a custom skin and click remap on the buttons, it won't remap.
Steps:..... Upload custom skin..
Expected Result: For the buttons to remap to furre colors.
Actual Result: Grey and red





Had to run to work when I posted first one. Just got off to post it the correct way.







I apologize I was using the wrong test version. That's what I get for rushing. XD

[Manni]

Hartens tend to become Rodents. Deer become lil' squeakers! >:3

Edit:

It works on Chrome just fine but for those relying on IE may get stuck on this screen in the new FurEd-

https://gyazo.com/abbaa19d32e6908b291e6c2d6d9562ee

Yup, yup.

[Armaina]

Bug Title: Digo's not working
Character name: Armaina
Web Browser: Waterfox 47.0.1 (firefox 47.0.1)
Furcadia test version: 31.0 RC9
Operating System: Windows 7
Details of the Bug: I'm also noticing a problem with Purrwings 'purrwing I only toggle back and forth between Mouse and Cat

https://dl.dropboxusercontent.com/u/2032433...%2013.25.14.png
https
://dl.dropboxusercontent.com/u/2032433...2013.25.20.png

edit- checked on another alt, with a Digo, same problem. Seems like all Digos are just not working.

How can we make this bug happen again?
Steps: try to change to a digo `purrwing or `freebee any non-hotkey digo.
Expected Result: Changing to the digo associated with the command.
Actual Result: you'll change to a mouse or some other base furre

[Malyn]

Bug: FreeBee art is largely off-screen in FurEd
Browser used: Firefox 47.0
Where: http://cms.furcadia.com/fured/
Pic of the bug: http://imgur.com/NGHazY2
How to reproduce: Click on FreeBee, let art load, be confused why it's down there.

I'd like to note that the Buggie, Froggen, Swoon, and Turkey are also afflicted.

[Iced]

Bug Title: Ctrl-F1 Not Taking Screenshot

EDIT: I thought about it, and I think because I had clicked a link and that annoying opening security dialog was opening, ctrl-f1 was not working. I relogged and it was working fine.

[Armaina]

Bug Title: Fured New Character Not Working
Character name: Talon Iskan
Web Browser: Waterfox 47.0.1 (firefox 47.0.1)
Furcadia test version: 31.0 RC9
Operating System: Windows 7
Details of the Bug: New characters made in Fured not accessible
https://dl.dropboxusercontent.com/u/2032433...%2014.41.19.png
Attempts to save a costume will error out

https://dl.dropboxusercontent.com/u/2032433...%2014.43.18.png
the character will even appear in the list

https://dl.dropboxusercontent.com/u/2032433...%2014.44.00.png
But when you attempt to play with the character you get an error.

I also noticed the character does not appear in my classic character list in my account so something about the fured does not seem to be applying new characters to the account.

How can we make this bug happen again?
Steps: Create a new character through the Fured interface only, doesn't matter what it is, then attempt to play with that character either through the play button or loading on the client
Expected Result: Character should be accessible to play
Actual Result: Errors appear when attempting to use character and the Furcadia client won't load at all.

[Alluvial]

Bug Title: Female bugge remap disparity
Character name: Alluvial
Web Browser: Firefox 47.0.1
Furcadia test version: 31a RC9
Operating System: Windows 7
Details of the Bug: The remaps on the female bugge avatar don't match the portrait or the butler. All three seem to have differing combinations so that none of them actually fully match another. Very confusing when trying to assign colors to a character!
How can we make this bug happen again? Change a character to a female bugge and edit the colors.
Steps: Load furre editor, select a character, select the female gender, select bugge species
Expected Result: That the highlighted color on the portrait/butler would match up with the avatar so that I could easily edit colors
Actual Result: Could not do this due to the disparity.

Screenshots:
http://i.imgur.com/ZZgFRao.png
http://i.imgur.com/Vy8BYvA.png
http://i.imgur.com/xqlCFse.png

[Cilo]

Bug Title: Cannot log in
Character name: Cilo
Web Browser: Google Chrome Version 51.0.2704.103 m
Furcadia test version: 31.0 RC 9
Operating System: Windows 7
Details of the Bug: I keep getting an error trying to log into my account after playing around with the new character editor (I just added wing colour). It seems like the error is with my description, so I removed all the links to see if that was the issue, but I cannot log in. Here's a photo of the error code I get: http://i67.tinypic.com/neuoh2.png
How can we make this bug happen again? Unsure, as I don't know the cause of the error.
Steps: -
Expected Result: logging into the game
Actual Result: this error: http://i67.tinypic.com/neuoh2.png

[Iced]

Bug Title: AngelCat Accent Remap Washed Out
Character name: Mystic Homes
Web Browser: 51.0.2704.103 m
Furcadia test version: 31.0 RC 9
Operating System: Windows 7 Home Premium
Details of the Bug: The animated preview of the angelcat shows a very... faded accent (halo) that doesn't feel true to the color, despite being clear in the portrait. Additionally, the portrait and butler differ on collar color. In the SDW the halo color seems improved for colors like royal blue (in comparison to the preview), but for yellow still seems washed out.

How can we make this bug happen again?
Steps: Select angelcat in the furre editor, pick yellow as an accent color.
Expected Result: The halo in the animated preview is obviously yellow, comparable to the current 8bit coloring.
Actual Result: The halo is washed out, appears almost white.

[Iced]

Bug Title: Squirrel Not Gendered
Character name: Mystic Homes
Web Browser: 51.0.2704.103 m
Furcadia test version: 31.0 RC 9
Operating System: Windows 7 Home Premium
Details of the Bug: The animated preview of the squirrel does not appear to be updating with gender changes, although all of the other defaults seem to do so. The butlers and portraits update correctly.

How can we make this bug happen again?
Steps: Select squirrel in the furre editor, change avatar gender.
Expected Result: The animated preview shows 3 different genders as you cycle through.
Actual Result: Only a single (either male or unknown I think) gender is shown.

[Space Core]

Bug title: Using second dreaming client causes visual tearing in regular client.
Character name(s): All of them I would assume.
Web browser: Opera?
Furcadia test version: 31a
Operating system: Windows 8.1
Details of the bug: After opening the test client, visual tearing and issues appeared on regular server, unsure how to fix this. Fixed by clearing cache.
Pictures here: http://imgur.com/a/q7dWc

How can we make this bug happen again?
Steps: Open both clients at the same time?
Expected result: Visual tearing?

[Shaun Dreclin]

Bug Title: Broken links in login window
Character name: Shaun Dreclin
Web Browser: Firefox 47.0
Furcadia test version: 31.0 RC9
Operating System: Windows 10 Pro 64 bit
Details of the Bug: Clicking the "Forgot Email?" "Forgot password?" and "User Agreement" links on the login window does nothing.
Steps: Run furcadia.exe and click one of the links at the bottom of the login screen.
Expected Result: Links should open a web browser.
Actual Result: They don't.

[Teennine]

Bug Title: Vinca Clouds
Character name: Teennine
Furcadia test version: 31.0 RC9
Operating System: Win 7
Details of the Bug: In the Vinca map, I can not walk on the cloud tiles to Zephiroth if I have my classic wings on my noble canine. If I turn off my noble and just become the default canine with my classic wings, I can then walk on the tiles. I have no other wings/nobles to test this on but I would guess it's probably the same for the other nobles with wings.

Not sure if this was known or not but I figured it'd be worth mentioning if it hasn't been already.

[Treeki]

Thanks all for the reports!

The issues with certain digos showing as rodents on Second Dreaming World have now been fixed -- no client update was necessary as we were able to upload fixed versions of those digos through the dynamic avatar system.

It works on Chrome just fine but for those relying on IE may get stuck on this screen in the new FurEd-

https://gyazo.com/abbaa19d32e6908b291e6c2d6d9562ee

Which version of IE are you using?

Bug Title: Fured New Character Not Working
[...]
Details of the Bug: New characters made in Fured not accessible

This should hopefully be fixed now, both for new alts and for Talon Iskan; please let me know if you still have trouble using any of the features!

Bug title: Using second dreaming client causes visual tearing in regular client.
[...]
Details of the bug: After opening the test client, visual tearing and issues appeared on regular server, unsure how to fix this. Fixed by clearing cache.
Pictures here: http://imgur.com/a/q7dWc

This is a known issue which occurs if you open Settings for the test client and click OK or Apply. It's actually a bug in the standard client where it picks up settings intended for the new client; the MissingNo-like scrambled pixels you see are what happens when the old code tries to load 32-bit FOX files!

You can still play on both worlds without issue; just beware of the fact that if you use the test client's settings, then any alts you have open on the regular server will have corrupted graphics until you log out and back in. (No need to clear your cache - just close the window and log back in.)

[Shaun Dreclin]

Bug Title: Bad password
Character name: Shaun Dreclin
Web Browser: Firefox 47.0
Furcadia test version: 31.0 RC9
Operating System: Windows 10 Pro 64 bit
Details of the Bug: Getting a "bad password" error when I try to log in. My password has special characters in it (I don't want to say which for obvious security reasons). It's a completely valid password that I log into the website with, but the client doesn't seem to like it.
Steps: Set account password to something with certain special characters in it and try to log in with the client.
Expected Result: Successful Login
Actual Result: "Error 2: Bad Password"

Edit: Whispered treeki details of which special characters are causing the issue

[Armaina]

This should hopefully be fixed now, both for new alts and for Talon Iskan; please let me know if you still have trouble using any of the features!

the client had an unknown issue and would keep freezing, so I tried another character, and that loaded fine. I tried Talon again and it worked. I notice she's still not in my character list on the site itself (the one on /services/accounts/) so it seems like I'd only be able to use her in the new client for now. A minor issue but still something I think worthy of note in case someone expected to use a Fured made character in the old client.

[Majas]

When you upload your dream, and you have your own skin. I have the buttons listed as remap able but they are not showing as remapping colors.

Bug

That bug was fixed in RC9, please make sure you are using the latest client! Your screenshot shows rc8