Topic: Mxm Wip Releases (Read 2962 times)

jlm5151 · « **Reply #375 on:** December 24, 2003, 07:18:00 PM »

Another bug to report....Screenshots are no longer working on the latest WIP. Tried a few different times, few different boots, no luck at all....

BenJeremy · « **Reply #376 on:** December 25, 2003, 04:48:00 AM »

QUOTE (jlm5151 @ Dec 24 2003, 11:18 PM)

Another bug to report....Screenshots are no longer working on the latest WIP. Tried a few different times, few different boots, no luck at all....

OK, I'll have to look at the input messages for screenshots and see if they are getting executed.

BenJeremy · « **Reply #377 on:** December 28, 2003, 03:39:00 PM »

"WIP" binaries have been updated.

Added Autodetect for DebugServer app.

Checked following:
- Screenshot works fine.
- Checked FTP directory creation/usage/removal "Rainbow 6" - works fine.

Added shifted versions of UI_DIR with the Gamepad input to the default tables in Internal.xml

Added build number, also added XDK version to About Box.

Biggest thing is the new DebugServer app. This will likely be renamed and updated a bit more, but in the meantime, "WIP" testers can get a taste of it and test it out in their environments.

geniusalz · « **Reply #378 on:** December 28, 2003, 03:54:00 PM »

The autodetect doesn't work with my network configuration.
I'm using a d-link router, with three DHCP IP's assigned to 2 computers, and an xbox.

I run the debug server app, then start up mxm, but nothing happens. I restarted mxm and the debug app a few times, with no result.

BenJeremy · « **Reply #379 on:** December 28, 2003, 05:07:00 PM »

QUOTE (geniusalz @ Dec 28 2003, 07:54 PM)

The autodetect doesn't work with my network configuration.
I'm using a d-link router, with three DHCP IP's assigned to 2 computers, and an xbox.

I run the debug server app, then start up mxm, but nothing happens. I restarted mxm and the debug app a few times, with no result.

Hmmmm.... I'm running a D-Link router as well, with DHCP.

Because the net output is enabled in the AutoExec, you can't override it (or you need to update it from the Internal.xml). Perhaps that's the problem?

It kicks in right after you hit the button to clear the "WIP" message box.

geniusalz · « **Reply #380 on:** December 28, 2003, 05:14:00 PM »

Yeah, its the autoexec.

BenJeremy · « **Reply #381 on:** December 28, 2003, 05:16:00 PM »

CODE

MSGLOG SETFILTER NET INFO ALL ON
MSGLOG SETFILTER NET WARNING ALL ON
MSGLOG SETFILTER NET ERROR ALL ON
MSGLOG SETFILTER NET CRITERROR ALL ON
MSGLOG SETLEVEL NET 0
MSGLOG SETOUTPUT NET 1.1.1.1
MSGLOG ENABLE NET ON
IF $MXMVersion$ !#^ "WIP" GOTO DONE
Set SecCount $timer$
Add SecCount 10000
CallScript _RenderMessageBox "This is a WIP Release$eol$Do not distribute$eol$%%$$"
:TIMELOOP
SET _GP_ANYBUTTON ""
SETFUNC MSG_ID IQGetMsgID ANY
; input nowait
; IF %_GP_ANYBUTTON% GOTO SKIPTIMERTEST
IF %MSG_ID% GOTO SKIPTIMERTEST
IF# %SecCount% > $timer$ GOTO TIMELOOP
:SKIPTIMERTEST
CallScript _ClearDisplay
:DONE
CallScript _CheckPrep

MSGLOG SETFILTER NET INFO ALL ON
MSGLOG SETFILTER NET WARNING ALL ON
MSGLOG SETFILTER NET ERROR ALL ON
MSGLOG SETFILTER NET CRITERROR ALL ON
MSGLOG SETLEVEL NET 0
MSGLOG SETOUTPUT NET 1.1.1.1
MSGLOG ENABLE NET ON

These are the critical lines... be sure to include them in your own AutoExec, to enable output to the "Net" in the first place. The SETOUTPUT IP is not important, as it is now ignored. I will fix this shortly so it's optional (and allows you to force the setting, if needed)

Author Topic: Mxm Wip Releases (Read 2962 times)