Common gotchas with Verge3D - Revision history

Sergey at 13:18, 8 June 2026

2026-06-08T13:18:17Z

← Older revision		Revision as of 13:18, 8 June 2026
Line 97:		Line 97:

	[[Category:Tutorials and How-Tos]]		[[Category:Tutorials and How-Tos]]
	{{#seo:\|type=~~website~~\|description=This page describes some typical problems you might experience when creating 3D web content}}		{{#seo:\|type=article\|description=This page describes some typical problems you might experience when creating 3D web content}}

2026-06-08T13:14:23Z

← Older revision		Revision as of 13:14, 8 June 2026
Line 1:		Line 1:
	~~{{#seo:\|type=article\|description=This page describes some typical problems you might experience when creating 3D web content}}~~
	This page describes some typical problems you might experience when creating 3D web content. These issues might cause problems with rendering or performance (or both).		This page describes some typical problems you might experience when creating 3D web content. These issues might cause problems with rendering or performance (or both).

Line 98:		Line 97:

	[[Category:Tutorials and How-Tos]]		[[Category:Tutorials and How-Tos]]
			{{#seo:\|type=website\|description=This page describes some typical problems you might experience when creating 3D web content}}

2026-04-25T16:27:20Z

Undo revision 1822 by Alexander (talk)

← Older revision		Revision as of 16:27, 25 April 2026
Line 96:		Line 96:

	[[File:App_manager_stop.webp\|634px]]		[[File:App_manager_stop.webp\|634px]]

	~~== See also ==~~

	~~[[How to debug Puzzles]]~~

	[[Category:Tutorials and How-Tos]]		[[Category:Tutorials and How-Tos]]

2026-04-25T16:17:24Z

← Older revision		Revision as of 16:17, 25 April 2026
Line 96:		Line 96:

	[[File:App_manager_stop.webp\|634px]]		[[File:App_manager_stop.webp\|634px]]

			== See also ==

			[[How to debug Puzzles]]

	[[Category:Tutorials and How-Tos]]		[[Category:Tutorials and How-Tos]]

2026-03-19T09:02:32Z

← Older revision		Revision as of 09:02, 19 March 2026
Line 97:		Line 97:
	[[File:App_manager_stop.webp\|634px]]		[[File:App_manager_stop.webp\|634px]]

	[[Category:Tutorials]]		[[Category:Tutorials and How-Tos]]

2026-03-05T14:21:07Z

← Older revision		Revision as of 14:21, 5 March 2026
Line 94:		Line 94:

	Essentially, App Manager uses background web server process attached to the particular user. Even after you perform a log out, this process stays as is and will prevent another App Manager session to be started. This might cause real confusion and various unpredictable bugs. Always stop the App Manager (via About dialog) before you switch the user. If you missed to do that, the most clean solution would be restating the system.		Essentially, App Manager uses background web server process attached to the particular user. Even after you perform a log out, this process stays as is and will prevent another App Manager session to be started. This might cause real confusion and various unpredictable bugs. Always stop the App Manager (via About dialog) before you switch the user. If you missed to do that, the most clean solution would be restating the system.

			[[File:App_manager_stop.webp\|634px]]

	[[Category:Tutorials]]		[[Category:Tutorials]]

2026-02-07T17:58:42Z

Switching system user when App Manager is running

← Older revision		Revision as of 17:58, 7 February 2026
Line 93:		Line 93:
	== Switching system user when App Manager is running ==		== Switching system user when App Manager is running ==

	Essentially, App Manager uses background web server process attached to the particular user. Even after you perform a log out, this process stays as is and will prevent another App Manager session to be started. This might cause real confusion and various unpredictable bugs. Always stop App Manager (via About dialog) before you switch the user.		Essentially, App Manager uses background web server process attached to the particular user. Even after you perform a log out, this process stays as is and will prevent another App Manager session to be started. This might cause real confusion and various unpredictable bugs. Always stop the App Manager (via About dialog) before you switch the user. If you missed to do that, the most clean solution would be restating the system.

	[[Category:Tutorials]]		[[Category:Tutorials]]

2026-02-07T17:57:23Z

← Older revision		Revision as of 17:57, 7 February 2026
Line 91:		Line 91:
	Upon adding this element to the page (e.g. to the canvas container), the browser will automatically apply the CSS style and modify the look of your page.		Upon adding this element to the page (e.g. to the canvas container), the browser will automatically apply the CSS style and modify the look of your page.

			== Switching system user when App Manager is running ==

			Essentially, App Manager uses background web server process attached to the particular user. Even after you perform a log out, this process stays as is and will prevent another App Manager session to be started. This might cause real confusion and various unpredictable bugs. Always stop App Manager (via About dialog) before you switch the user.

	[[Category:Tutorials]]		[[Category:Tutorials]]

2026-01-16T08:20:35Z

← Older revision		Revision as of 08:20, 16 January 2026
Line 90:		Line 90:

	Upon adding this element to the page (e.g. to the canvas container), the browser will automatically apply the CSS style and modify the look of your page.		Upon adding this element to the page (e.g. to the canvas container), the browser will automatically apply the CSS style and modify the look of your page.

	~~== Inconsistent colors when using Alpha Hashed (Coverage) transparency ==~~

	There is a known issue when dealing with alpha hashed transparency. When rendering, the browser mixes-in the background color taken from the <canvas> element even if the scene background is explicitly set to be non-transparent. Use the following puzzle to make alpha hashed transparency work properly:

	~~[[File:Background_black.png\|758px]]~~


	[[Category:Tutorials]]		[[Category:Tutorials]]

2026-01-16T08:17:42Z

Inconsistent colors when using Alpha Hashed (Coverage) transparency

← Older revision		Revision as of 08:17, 16 January 2026
Line 95:		Line 95:
	There is a known issue when dealing with alpha hashed transparency. When rendering, the browser mixes-in the background color taken from the <canvas> element even if the scene background is explicitly set to be non-transparent. Use the following puzzle to make alpha hashed transparency work properly:		There is a known issue when dealing with alpha hashed transparency. When rendering, the browser mixes-in the background color taken from the <canvas> element even if the scene background is explicitly set to be non-transparent. Use the following puzzle to make alpha hashed transparency work properly:

	[[File:Background_black.png\|~~1000px~~]]		[[File:Background_black.png\|758px]]


	[[Category:Tutorials]]		[[Category:Tutorials]]