[Bug] Editor bug <Resolved>

Post a reply


This question is a means of preventing automated form submissions by spambots.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: [Bug] Editor bug <Resolved>

Re: Editor bug

by Lewa » Sun Apr 02, 2017 10:26 pm

BlueCrescentMoon wrote:
Sun Apr 02, 2017 12:22 am
Mhm, just felt the need to show it off in case you hadn't noticed it. Any idea why it likes to do that, just curious.
It's good that you report such bugs. (You would be surprised what kind of bugs i miss and only find out about them from testers of the game.)
I found the issue.
Basically, the all 3D models of the selection preview (of blocks,the player startpoint, etc...) use a special shader in the render loop. The only exception are the spheres/hidden gems (they are now called "spheres" in the beta.). They have an own seperate shader. The bug was that after setting the shader from a sphere, it wasnt reseted to the default selection shader (and thus all selected blocks which were internally rendered after a sphere had this display bug.)

Re: Editor bug

by BlueCrescentMoon » Sun Apr 02, 2017 12:22 am

Mhm, just felt the need to show it off in case you hadn't noticed it. Any idea why it likes to do that, just curious.

Re: Editor bug

by Lewa » Sat Apr 01, 2017 4:41 pm

This will be fixed.
Seems to be a bug which overwrites the shader of the placement-preview model.

[Bug] Editor bug <Resolved>

by BlueCrescentMoon » Sat Apr 01, 2017 2:47 pm

Something small, I'm sure it doesn't matter much but, when selecting a gem and then a block the block turns a pure white.This occurs only when selecting both objects, in that order.

Screenshot
[+] Spoiler
Image

Top