UDK tricks

[Gildor]

How to start UDK with a log:

Code:

udk.com -log

this command will force UDK executable to create a console window and print all logs there. If you're launching UDK.com from the console window, UDK will detach from this window and allocate another one.
I've written a small application which will let you to start UDK with logging to the same console where it was started from. The program is in attachment, including the source code.

How to use it:

• place udkc.exe into the directory UDK/Binaries/Win32
• start udkc.exe [arguments for udk.exe]

The program will automatically add "-log" switch, so it is not required. You may also start editor with udkc.exe too.

udkc.exe will not work with Win64 version of UDK. Also, it could not work on some systems (I don't know why, may be because of antivirus software).

I've asked Epic Games team to include this fix into the UDK executable itself so when "-log" switch is specified it will reuse existing console window when possible. Epic were agreed to do this after some tests, so probably this fix will appear in one of the future UDK builds (not fixed in DEC-2011 build).

[вложение удалено Администратором]

[Gildor]

Some additional notes about enabling hidden targets in UnrealFrontEnd.

• When you will enable licensee (non-UDK) mode, UnSetup button will disappear and it will be replaced with UnProp button. UnProp is another system for making game distributions available to engine licensees. If you want to use UnSetup you should either temporarily enable UDK mode or use command line to build game distribution.
• I have informed Epic Games programmers about unavailability of PCServer and PCConsole targets and about missing UnSetup button. One of developers has replied that he has a task to do this but this task has too low priority to implement. So, in other words, modifying build.properties file to enable licensee mode is quite legal thing