#141 posted by niger on 2018/01/16 15:33:40
Hey, i think this was asked and replied:
https://www.q3df.org/forum/viewtopic.php?f=15&t=789&start=130#p11412
Just change base directory to use
Or configure, as for mod, and use its directory for wads
Or just make separate fresh install for mapping
Numerous possibilities kinda
#142 posted by Kinn on 2018/01/16 15:44:41
basegame="id1"
So, is this basegame field only used to tell the editor where to find the wad files? It's not used for anything else?
#143 posted by niger on 2018/01/16 16:28:03
It's used for anything, which is normally loaded from id1
Also is used for build menu variables
We'v just figured out, that it also loads
Users\Username\Documents\My Games\q3a\ (q3a is cfged by .game: prefix=".q3a")
I think it's a good idea to add option to load one more specific directory, once it's supported in q1 and q3 compilers
I See
#144 posted by Kinn on 2018/01/16 16:42:08
To be honest I think it would be a really useful feature for netradiant to have a "wad path" option, that can be an absolute path, totally independent to anything else.
Another Question
#145 posted by Kinn on 2018/01/16 16:54:37
Using netradiant's build menu, is it possible to specify an output directory for the bsp that's different to the directory of the map file?
#146 posted by niger on 2018/01/16 17:06:05
It's up to compiler, radiant does nothing with .bsp
Ah Ok
#147 posted by Kinn on 2018/01/16 17:38:14
yeah the compiler will chuck the .bsp in the same folder as the .map when fed the commands as generated by the netradiant build menu.
#148 posted by niger on 2018/01/16 18:06:04
Build menu commands can be configured accordingly, if compiler supports saving bsp to arbitrary path.
#149 posted by Kinn on 2018/01/16 19:26:12
Build menu commands can be configured accordingly, if compiler supports saving bsp to arbitrary path.
OK I've just messed around with the build menu xml file and I appear to have got it configured how I want now, cheers.
Late To The Party
#150 posted by Kinn on 2018/01/18 01:32:55
#121 posted by niger [5.19.80.46] on 2017/08/02 19:26:48
Some tip on requested 'align texture with given face edge' feature here:
https://youtu.be/qA9eNOkD1iY
When he got to the bit here:
https://youtu.be/qA9eNOkD1iY?t=65
And started aligning the arch textures by making them "flow" seamlessly over from the top faces with the texture paste shortcut...I won't lie, I did a little sex wee.
:O
#151 posted by killpixel on 2018/01/18 01:39:42
that's awesome, wish I knew this sooner.
Clear All
#152 posted by negke on 2018/01/31 12:07:34
About the "Clear all" button in the entity tab: probably not getting that much use overall, although I do use it every so often. However, in its current form it only works on brush entities - using it on point entities causes problems, because it removes the origin field. Can this be changed so that the origin field is kept if the button is used on a point entity?
#153 posted by niger on 2018/01/31 12:30:16
Sounds like making sense from the first look.
Don't other means replace wished behavior well? (del key to del unwanted keys or save origin in key/val fields, then restore)
Update!
#154 posted by niger on 2018/03/04 19:00:07
Netradiant And Windows Aero
#155 posted by killpixel on 2018/03/04 20:02:03
specifically aero glass which is disabled while netradiant is open. Anyone know why this is/has a solution?
#156 posted by niger on 2018/03/04 20:29:06
netradiant-custom shouldn't disable aero, unless you put -aero command line parameter
Noice
#157 posted by Kinn on 2018/03/05 11:58:34
That is one spicey changelog!
Will give it a spin this evening :)
Hotfix!
#158 posted by niger on 2018/03/05 12:27:48
Radiant/aero
#159 posted by killpixel on 2018/03/07 02:36:51
google says it's a thing, though not very common... still can't find a solution though. must be my system.
@killpixel
#160 posted by niger on 2018/03/07 20:15:36
-I recall internet topics about windows, disabling aero for applications sometimes; there was a solution too; reason to disable was wrongly detected low performance iirc
-There is a way to disable aero via compatibility settings of windows application
-Normal Netradiant is disabling aero to fix rendering issue; Custom one does not, since it's fixed (are you speaking about custom one?)
Niger
#161 posted by killpixel on 2018/03/08 18:50:09
are you speaking about custom one?
Occurs with both Ingar's package and this custom one. I haven't tested others. I'm sure it's my system, I just haven't investigated it very deeply.
Cmdline
#162 posted by ww on 2018/03/31 07:50:41
-q1.game-CamHeight 724 -q1.game-XYWidth 951 -q1.game-fieldOfView 90
to match in game and cam window
Rariant/Aero Update
#163 posted by killpixel on 2018/05/04 18:14:29
The issue doesn't occur when using an old gpu and legacy nvidia drivers. Tinkering with latest drivers has proven futile so far...
Update!
#164 posted by niger on 2018/05/16 20:43:49
https://github.com/Garux/netradiant-custom/releases
Clipper and brush creation, working in camera, among other things.
NetRadiant: TrenchBroom Edition
#165 posted by Kinn on 2018/05/17 11:15:40
Nice! Will give this a whirl :)
|