Need Help with Assassin's Creed Debug

So I recently bought a debug version of Assassin's Creed from Wombat and I know almost all the debugging features except one. I am told there is a debug menu in the game but Wombat was only able to get it to show up twice by accident.
A keyboard is used for almost all the debugging (except for flying/no clip).

Is there a way I can find out what I need to do to access the debug menu (I am told it can be accessed via the keyboard)?
Also the disc installs the entire game on the HDD so I have access to all the files.

Any help would be much appreciated.

 

Have you tried specific button combinations with the D-Pad? If not can you list what you HAVE tried?

Also will we be seeing a release of the build soon? I'd like to see this for myself as I have yet to touch a single AC game and think a debug one would be fun

 

I tried almost every combo of buttons I can think of on the keyboard and the controller. I did find out that CNTRL + Z freezes the game and pressing J or * temporarily freezes the game.

And I had to pay a lot of money for the disc so for now I do not plan on releasing the game.

 

It must be a strange combo of buttons on the keyboard. Maybe even 3 keys instead of 2 who knows. I was hoping there was a way to find out via the game files.

 

I'd be willing to give it a shot and remove the data when It's figured out.
I remember a similar thing when I was handling the Megaman Legends 2 debug build. That and the WWE13 build has some stuff going on that was a pain in the ass to figure out so I'm very aware how stressful this can be.

 

idk. I might be willing to send you the main xex file. I don't necessarily want to send the whole game to anyone. At least not yet.

 

I can respect this. I just dont know what AC game it is and it doesn't help when theres so many of em

 

Its the first game. I don't think I would buy a debug copy of one of the later ones lol
But if you want I can send you the xex file.

 

Sure im down. Just need to get a copy of the game itself lol.

 

PM Sent.

 

For future reference here's what we've figured out regarding commands.
Still no success on the debug menu but who knows, it will probably show itself in the future. Oh and @Borman any ideas on what may bring up a debug menu of sorts? We both have exhausted almost every combination possible, and I dont know whether or not the file scimitar.ini can allow things to be altered but it's worth a shot.

Inside scimitar.ini we have these notes

Code:

[XENON]
BFLOCATION=LocalHD
DATASERVICE=
COMMANDLINE= /fast /noconsole /nofps 

Commands are here

Code:

+++Keyboard+++

---Visual related---

--Model Specific--
F7 - display wireframe
W - wireframe related

--Lighting specific--
F4 - Lighting changes
Q - Lighting related
S - Lighting related as well
F - Also lighting related
Enter (numpad) - more lighting changes
6 (numpad) - yet more lighting changes


--Freeze related--
*J - freezes momentarily*
*U - freezes permanently until pressing it again*
*[star] (numpad) - freezes the game temporarily*
*Spacebar - pauses game til pressed again*
*CRTL+Z - freezes permanently*
*CTRL+F11 - freezes indefinately*
*7 (numpad) - Freezes everything except the player*


--Other--
F3/R - resets mission?


+++Gamepad+++
LB+RB+A - teleports you in a direction for progression?
L3+R3 - Flycam/mode
      - RT to fly faster
      - RB to fly even faster

 

Not sure, I havent had an AC prototype and every game is different

 

Remove that "noconsole"? Then try opening console with the tilde key or whatever it's called?

Or maybe change it to say console or heck remove everything in that line.

 

I can take a look if you want. I don't need any assets, just the binary and whatever startup files there are. I don't have a 360 so no guarantees.

 

I would like to take a look at the xex as well.

 

Sorry but at the moment I am not sending the file to anyone else. I already have a couple people here helping me out. Thank you though.

 

And I can confirm that even if I run the game without the .ini file all the debug options still work. So I don't really know why the .ini file is there in the first place.

 

I tired removing the entire line along with the file itself and it does not affect the debug options. I have literally pressed every key on my keyboard lol

 

And this build is from a month before its release according to the age of the files.

 

Hmm My guess is that you need to set a switch of some kind to enable console but what that might be I have no idea, Maybe something like /devmode or /debug or something.