Tweet
It is actually very simple to customize the build menu for virtuoso and I intend to teach you many simple things that will add a lot of power to your build. I will leave no stone unturned here in an observation sense.
The first step is to open radiant then click build, followed by clicking customize. This will bring up the console featured in the image below.
There are a few things to note about this image. For one, any name or command is customizable by double clicking it. For two, you will notice that -threads is assigned the value of 1. I did this because everyone has at least one processor on their computer. You can double click that command line and change 1 to any number up to the amount of processors cores on your computer. The higher you make the number, the more system resources you will use for the vis process and the faster it will complete. I was unaware of this when I built the build menu, but light also accepts the thread parameter. Bengt Jardrup initially removed this feature because it didn't work, but other coders put this feature back in and made it work.
The above image also expresses a few examples. For one you will notice that i completely changed the name of the build to reflect it's new features. You will also notice that I added the -sunlight and -sunmangle switches that that compiler supports. What may not be obvious is anytime you are using a switch that allows for more than one value, all of those values must be placed in quotes and separated by a comma.
There is something important to note that these images do not show you.
1) make sure you save your map as soon as you change a build because it is actually a little glitchy and you may lose your changes if you don't
2) once you save, if you were using the default_build_menu.xml file, which is the default if you have not made any adjustments, you will no longer be using that file. (note: the adjustment you can make is listed in the read me that comes with the virtuoso_q1 download). What happens is, NetRadiant will save a new Build_Menu.xml in settings/1.5.0/virtuoso_q1.game and that will be the file that loads from now on.
2a) If you already pulled a Build_Menu.xml from the build_menus folder, which comes with virtuoso, and placed it in settings/1.5.0/virtuoso_q1.game (AKA the adjustment), NetRadiant will overwrite that file. It is important to consider this because now your backup Build_Menu.xml in the build_menus folder will not be the same as the one NetRadiant just overwrote. You may want to overwrite your backup with this new file in order to maintain your changes.
3) another nominal and unimportant change is the build menu that NetRadiant just wrote will have all quotes replaced with the escape code for a quote. (I can't type it cause it will just show up as a quote). The only reason this may matter at all is if you were to modify that document by hand, it will look insane when you open it.
That's it, most of what I just said is FYI stuff. The only thing you really need to focus on is:
1) click build/customize
2) make your adjustments
3) multi-valued switches need to be comma separated and in quotes
4) always save your map right after
x) make sure you are adding switches that actually belong to that compiler. Read the docs.
The first step is to open radiant then click build, followed by clicking customize. This will bring up the console featured in the image below.
There are a few things to note about this image. For one, any name or command is customizable by double clicking it. For two, you will notice that -threads is assigned the value of 1. I did this because everyone has at least one processor on their computer. You can double click that command line and change 1 to any number up to the amount of processors cores on your computer. The higher you make the number, the more system resources you will use for the vis process and the faster it will complete. I was unaware of this when I built the build menu, but light also accepts the thread parameter. Bengt Jardrup initially removed this feature because it didn't work, but other coders put this feature back in and made it work.
The above image also expresses a few examples. For one you will notice that i completely changed the name of the build to reflect it's new features. You will also notice that I added the -sunlight and -sunmangle switches that that compiler supports. What may not be obvious is anytime you are using a switch that allows for more than one value, all of those values must be placed in quotes and separated by a comma.
There is something important to note that these images do not show you.
1) make sure you save your map as soon as you change a build because it is actually a little glitchy and you may lose your changes if you don't
2) once you save, if you were using the default_build_menu.xml file, which is the default if you have not made any adjustments, you will no longer be using that file. (note: the adjustment you can make is listed in the read me that comes with the virtuoso_q1 download). What happens is, NetRadiant will save a new Build_Menu.xml in settings/1.5.0/virtuoso_q1.game and that will be the file that loads from now on.
2a) If you already pulled a Build_Menu.xml from the build_menus folder, which comes with virtuoso, and placed it in settings/1.5.0/virtuoso_q1.game (AKA the adjustment), NetRadiant will overwrite that file. It is important to consider this because now your backup Build_Menu.xml in the build_menus folder will not be the same as the one NetRadiant just overwrote. You may want to overwrite your backup with this new file in order to maintain your changes.
3) another nominal and unimportant change is the build menu that NetRadiant just wrote will have all quotes replaced with the escape code for a quote. (I can't type it cause it will just show up as a quote). The only reason this may matter at all is if you were to modify that document by hand, it will look insane when you open it.
That's it, most of what I just said is FYI stuff. The only thing you really need to focus on is:
1) click build/customize
2) make your adjustments
3) multi-valued switches need to be comma separated and in quotes
4) always save your map right after
x) make sure you are adding switches that actually belong to that compiler. Read the docs.