What happens when the fisheye effect reaches its limit? 
3sal2 (talk | contribs) 02:51, 4 January 2013 (UTC)
Should we add that there are certain glitches
There are certain known glitches with graphic effects, such as edges registering as black. Should we put that here so that people will know in advance before they make projects that rely on the edge not being black and use graphic effects, and/or so that they don't report it again?
--
ItchyCatIII (talk | contribs) 23:25, 30 September 2015 (UTC)
- That would be nice. Someone else should do it though, because I don't know much about graphic effect glitches.
Nambaseking01 (talk | contribs) 15:13, 28 December 2019 (UTC)
Fisheye Section Problem
 Resolved (since 05:19, 19 August 2023 (UTC))
|
|---|
The fisheye section only refers to Scratch 2.0 and Scratch 1.4, but I don't know how the system works in 3.0. Can someone please change the words to pastenses and also put the 3.0 system in there (if this is the same as 2.0, then basically change the 2.0 to "2.0 and 3.0"). Thanks! 
Edit: Apparently the Whirl section also has this problem, can someone please also fix that?
Nambaseking01 (talk | contribs) 15:13, 28 December 2019 (UTC)
- Fixing Some of the Images.
LokiBlaster | Talk Page | Contributions 21:00, 17 November 2021 (UTC)
- Updated limits for whirl and fisheye effect, as well as corrected the mosaic effect limit, though work still needs to be done on the page. The images haven't been updated to 3.0 yet, and older versions need to be tested.
Ametz807 (talk | contribs) 16:28, 25 July 2022 (UTC)
The whirl section contains incorrect information
On the page, it states "Any number whose absolute value is more than or equal to 194967423051954×10^26 will cause the sprite to turn into a hole.", but I feel like 194967423051954×10^26 is a completely arbitrary number for a concept as vague as holes. In addition, the "Any numbers larger than 1.94967423051954×1040, however, will cause the sprite to disappear." is wrong, but will instead produce a box confined in the bounding box of the sprite. The reason it doesn't seem to appear is because the whirl effect takes the bottom right pixel and makes that the box color, but since most sprites have a fully transparent color as the bottom right pixel, it's very common to have the box not show up. Shouldn't the whirl effect section be changed to account for these problems? Ametz807 (talk | contribs) 15:30, 26 July 2022 (UTC)
- Thanks for notifying. I tested again and found my previous statement being incorrect. However, it seems the box color is taken from the top left of the sprite. You can view my test project here.
-iviedwall- ‖ talk contributions 🐱 03:53, 27 July 2022 (UTC)
- Interesting you see the top left pixel, as the color I see here is red. Ametz807 (talk | contribs) 15:17, 27 July 2022 (UTC)
- I see blue. This might depend on the browser, OS, or GPU.
Maximouse (talk | contribs) 16:03, 27 July 2022 (UTC)
- Turns out it depends on your browser and OS, and the rectangle might not even appear depending on your combination. From what I've tested, Safari and Firefox on Windows 10 does nothing, Safari on MacOS Monterey (12) makes the sprite completely vanish, and FireFox on MacOS Monterey (12) makes an oval appear. Because of this, I feel like the box thing should be removed and instead should say something that states how effects could differ depending on your OS/Browser. Ametz807 (talk | contribs) 19:06, 27 July 2022 (UTC)
- Turns out it depends on your browser and OS, and the rectangle might not even appear depending on your combination. From what I've tested, Safari and Firefox on Windows 10 does nothing, Safari on MacOS Monterey (12) makes the sprite completely vanish, and FireFox on MacOS Monterey (12) makes an oval appear. Because of this, I feel like the box thing should be removed and instead should say something that states how effects could differ depending on your OS/Browser.
- I see blue. This might depend on the browser, OS, or GPU.
- Interesting you see the top left pixel, as the color I see here is red.
I see. I use Chrome 103 and Windows 10 and it seems like you are using Mac OS 10 (on ScratchStats) so apparently it will appear different on different browsers and devices. 
So I'm adding more information to that part. Thanks for pointing that out! .png){kind=small}
-iviedwall- ‖ talk contributions 🐱 04:14, 28 July 2022 (UTC)
- Turns having the same OS and browser isn't enough, and some other factor is determining the color, as seen here, so the factor needs to be found. Ametz807 (talk | contribs) 14:17, 28 July 2022 (UTC)
- I see. I put a stub template in the section. -iviedwall- ‖ talk contributions 🐱 14:27, 28 July 2022 (UTC)
- I see. I put a stub template in the section.
Weird color effect quirks
When the color effect is used, if the color's saturation value is less than 9, the saturation value is set to 9, and the color value is set to 0 (although this is applied before the color effect change, so the color component will most likely not be 0). Similarly, when a color's brightness value is less than 5.5, then the brightness value is set to 5.5, the saturation is set to 100, and the color effect is set to 0 (which keep in mind, is before the color effect is applied, so the resulting color component will most likely not be 0). This is strangely not a bug, but intentional (seen here), so shouldn't this be mentioned somewhere? Ametz807 (talk | contribs) 15:28, 27 July 2022 (UTC)
- Yes. This even have a section on the page Scratch Bugs, so I guess we may need to remove sections related to this because ti's intentional and not a bug. -iviedwall- ‖ talk contributions 🐱 04:32, 28 July 2022 (UTC)
Is the Other section really necessary?
We don't need a section for every single commonly suggested thing on Scratch; there's nothing on the Wiki about dark mode, a much more commonly suggested feature, for example - what makes this special?
mybearworld • Talk • Contributions • Profile 19:08, 31 March 2023 (UTC)
