Network baking - Revision history

Mr F at 14:30, 28 April 2024

2024-04-28T14:30:48Z

Mr F at 08:34, 16 August 2023

2023-08-16T08:34:27Z

Mr F at 17:11, 15 December 2022

2022-12-15T17:11:19Z

Mr F at 17:10, 15 December 2022

2022-12-15T17:10:18Z

Mr F: /* Network baking */

2020-03-11T20:16:06Z

‎Network baking

Mr F: Created page with "== Network baking == Network baking interface This feature is currently in beta. * Doesn't perform distributed rendering yet, but you can offload b..."

2019-05-30T09:33:07Z

Created page with "== Network baking == thumb|Network baking interface This feature is currently in beta. * Doesn't perform distributed rendering yet, but you can offload b..."

New page

== Network baking ==
[[File:Ftclient.jpg|thumb|Network baking interface]]
This feature is currently in beta.
* Doesn't perform distributed rendering yet, but you can offload baking to another PC;
* The idea is to use it over LAN, not over Internet (large data transfers);
* Server PC doesn't need Unity installed;
* Client PC doesn't require Nvidia GPU.

To use network baking:

1. Install Bakery on both client and server PC. If you don't have Unity on the server, just copy Assets/x64/Editor/Bakery folder.

2. Run ftServer.exe on server PC. Simply double-clicking it will work, but its temp folder will default to Users/Your username/AppData/Local/Temp/ftServer. If you want it to be in another folder, you'll need to specify it as an argument to ftServer either via command line, a bat file or with a simple shortcut: ''ftServer pathToTemp''.

3. On client PC, set settings to Experimental, scroll the window down and check "Bake on remote server". Type the server IP in (make sure you can ping this IP).

4. Click "Connect to server". Now Bakery window will monitor current server status. If it says "Idle", you're ready to go.

5. Click the regular Render button. Status should now display baking progress.

6. After the bake is done, it will say "Idle" again. Click "Get data" to import and apply the lightmaps.

{{note|ftServer can be only launched manually. Bakery will never run it automatically.<br>Even though ftServer is designed with extensive validation and crash resistance in mind and it's very unlikely to be targeted, it is not recommended to expose it to Internet for security purposes. Make sure Windows only allows your trusted LAN to interact with ftServer. Using NAT and routers as hardware firewalls is a good idea.}}

← Older revision		Revision as of 14:30, 28 April 2024
Line 21:		Line 21:

	{{note\|ftServer can be only launched manually. Bakery will never run it automatically.<br>Even though ftServer is designed with extensive validation and crash resistance in mind and it's very unlikely to be targeted, it is not recommended to expose it to Internet for security purposes, if the LAN option is viable. Make sure Windows only allows your trusted LAN to interact with ftServer. Using NAT and routers as hardware firewalls is a good idea.}}		{{note\|ftServer can be only launched manually. Bakery will never run it automatically.<br>Even though ftServer is designed with extensive validation and crash resistance in mind and it's very unlikely to be targeted, it is not recommended to expose it to Internet for security purposes, if the LAN option is viable. Make sure Windows only allows your trusted LAN to interact with ftServer. Using NAT and routers as hardware firewalls is a good idea.}}
		+
		+	{{note\|By default, ftServer uses port 27777. You can change it by modifying '''serverPort''' in ftClient.cs and running ftServer with "-p" argument via command line. For example, for port 27778: '''ftServer "C:/myTempPath" -p 27778'''}}

← Older revision		Revision as of 17:11, 15 December 2022
Line 20:		Line 20:
	6. After the bake is done, it will say "Idle" again. Click "Get data" to import and apply the lightmaps.		6. After the bake is done, it will say "Idle" again. Click "Get data" to import and apply the lightmaps.

−	{{note\|ftServer can be only launched manually. Bakery will never run it automatically.<br>Even though ftServer is designed with extensive validation and crash resistance in mind and it's very unlikely to be targeted, it is not recommended to expose it to Internet for security purposes. Make sure Windows only allows your trusted LAN to interact with ftServer. Using NAT and routers as hardware firewalls is a good idea.}}	+	{{note\|ftServer can be only launched manually. Bakery will never run it automatically.<br>Even though ftServer is designed with extensive validation and crash resistance in mind and it's very unlikely to be targeted, it is not recommended to expose it to Internet for security purposes, if the LAN option is viable. Make sure Windows only allows your trusted LAN to interact with ftServer. Using NAT and routers as hardware firewalls is a good idea.}}

@@ Line 8: / Line 8: @@
 To use network baking:
-. Install Bakery on both client and server PC. If you don't have Unity on the server, just copy Assets/x64/Editor/Bakery folder.
+. Install Bakery on both client and server PC. If you don't have Unity on the server, just copy Assets/Editor/x64/Bakery folder.
 . Run ftServer.exe on server PC. Simply double-clicking it will work, but its temp folder will default to Users/Your username/AppData/Local/Temp/ftServer. If you want it to be in another folder, you'll need to specify it as an argument to ftServer either via command line, a bat file or with a simple shortcut: ''ftServer pathToTemp''.

@@ Line 2: / Line 2: @@
 [[File:Ftclient.jpg|thumb|Network baking interface]]
 * Doesn't perform distributed rendering yet, but you can offload baking to another PC;
-* The idea is to use it over LAN, not over Internet (large data transfers);
+* The idea is to use it over LAN or very fast Internet (large data transfers);
 * Server PC doesn't need Unity installed;
 * Client PC doesn't require Nvidia GPU.