the cutting room mirror

Oct. 13, 2006 Builds

This article has a talk page!
view on tcrf.net

This is a sub-page of Proto:Viva Piñata (Xbox 360).

Debug-Enabled Builds#

While there are a number of functions that are active globally in the debug-enabled executables, some are only present on PinataParadiseT and PinataParadiseDv.

Global Functions#

  • The project menu can be activated by pressing LB.
  • The debug menu can be triggered by holding Back and pressing X while in your garden. The contents of the menu will differ depending on what's currently selected.
    • Doing the combo on anything other than the below cases will pull up the generic debug menu.
    • Doing the combo while hovering over a Pinata will pull up the Pinata-specific debug menu.
    • Doing the combo while hovering over a Helper will pull up the Helper-specific debug menu.

Testing Build-specific Functions#

  • Debugging text for player information as well as information about active Pinatas and Helpers is active in this build.
  • The Store button present in the generic debug menu works in this build.

Text Differences#

  • All of the text differences in the Oct. 10th, 2006 build are present here.
  • The Emergency Quit message was altered later on to include the "Xbox 360" name and extra capitalization.

Tag

Prototype

Final

aid_loctext_pinata_pip_emergencyquit (Oct. 10, 2006 at 14:58:47) -> (Oct. 16, 2006 at 11:45:24)

pip__0

You’ve played for a long time without a break and I need a rest.
Unfortunately because you have been playing without a memory unit there is no way for us to store your progress.
I hope you’ve enjoyed the game so far, come back and play again soon.

You’ve played for a long time without a break and I need a rest.
Unfortunately because you have been playing without an Xbox 360 Memory Unit there is no way for us to store your progress.
I hope you’ve enjoyed the game so far, come back and play again soon.

Build Information#

In a number of the executables found in this dump, build strings are present, either intended for logging purposes or to be drawn on the screen.
Ones printed to the console specify when the main app (app_main_debug.c) was built while on-screen ones (usually shown on assertions) are more simplified, but show the user and system that made the build. In this case, the user is reported as Eoin O'Flynn.

Executable

Combined Build String(s)

PinataParadiseDv

Console: Piñata Paradise: DEVELOPMENT build with RELEASE libraries for [app_main_debug.c compiled on Oct 13 2006 at 11:08:35] On-Screen: Build 03.10.2006.2428Dv
Type Development
At 06.05.51
By eoflynn
On eoflynn

PinataParadiseT

Console: Piñata Paradise: TESTING ROM build with RELEASE libraries for [app_main_debug.c compiled on Oct 13 2006 at 14:02:55] On-Screen: Build 03.10.2006.2428T
Type Testing
At 06.05.51
By eoflynn
On eoflynn

PinataParadiseN
PinataParadiseNO
PinataParadiseROC

On-Screen: Build 03.10.2006.2428
Type Release
At 06.05.51
By eoflynn
On eoflynn

Debugging Messages#

In the debug-enabled executables, plenty of messages intended to be printed out to a console (or printed through assertions) can be found.
Only the more interesting ones will be mentioned here, as a lot of the messages are fairly generic. Sorry if your day was spoiled, PC. :(

Message

Note(s)

Main Assertion

"The order of the strategy software table (actor_strategy_pinata_id_list.h) at entry '%s' doesn't match the excel interrupt method table (%s) - speak to JP if unsure of how to fix."

Prints from the function "meValidateStrategyNames", mentions a header file.
"JP" in this context is referring to "John Pegg".

"The string contains a curly apostrophe. The source has probably been cut and pasted in to the loctext file from Word. Search and replace with the straight apostrophe."

Prints from the function "glStringUnicodeConvertUnicode2Ansi", directly mentions Word.

"Erm, this shouldn't be happening!"

Prints from the function "actorBodyInputGetActionForButton".
Only if it can't get which button it's masking.

"Failed to create the factory crate, I dunno when that can happen so I made this to annoy you (GL)"

Prints from the function "meTickFactoryChallenges".
"GL" in the context is likely referring to "Gareth Lough".

"Well done - you successfully proved to Pete that this section of code is necessary! Thanks... and sorry for crashing!"

Prints from the function "MePlayAudio".

"You can't have -100% life, that's silly!"

Prints from the function "pinataactorStatsGetLifespanModifier".

debugLogMessage

"The Professor cannot reach his intended target at the last hurdle - quitting the strategy now :("

Prints from the function "entityStrategyPinataAnimalIdRuffianStealTick".

"Choose a USABLE tag Dumbass!"

Prints from the function "meHostStructCallback" for Eoin o'Flynn's work scene.

debugLogBufferedMessage

"Writing CSV file: ..\\logs\\stats\\character_profiling_pinata_1.0.csv ..."
"(note that the game may appear to freeze if you have the file open in Excel on the host since it will wait for the file to become unlocked!)"

Directly mentions Excel.

" The reset button was de-pressed :-("

Prints from the function "meStatus" under the Host Web Services.

"%s reset button was de-pressed :-("

Prints from the function "meShortStatus" under the Host Web Services.

"Nope, only works on *actors*. But please feel free to try again..."

Prints from a function regarding controlling actor feelings.

"This is just wrong - WB 22/05/2005, look at the code"

Prints from the tick function of Richard Geary's work scene.
"WB" in this context is referring to "Will Bryan"

debugConsoleSupportPrintfError

"DASTARDOS - Every method of generating a path to our target failed. Don't know how to recover from this one!
Dastardos will attempt to walk through any obstacles that remain in his way, but this might fail. Please show to PC and spoil his day! :("

Prints from the function "supportPinataHelperDastardosGeneratePathToPoint".
"PC" in this context is referring to "Peter Campbell".

"Fix it or ye will be forced to swab the deck, or even be keel-hauled ye sea dog.. arrr"

Prints from the function "uiSupportVideoSafeAreaTestDoTest".
Only if the test concludes that it's out of the video safe area.

On-Screen Printing

"Hello World! (How corny is that?)"