Build does not honour menu return commands?

Question

Has anyone encountered this problem? When simulating within DVDSP4, all menu return commands go to the correct menu page (I have 22 menus!). BUT . . . when I do a "build" of the file, the built file does not honour ALL of the menu return commands, just some of them!?!
For almost all of the buttons on each menu screen, I am using stories to locate a specific chapter on a single video track. Each story item correctly designates the menu return - pointing back to that specific menu button from which it originated.
Simulation mode works fine - built file (using Apple's DVD player or burnt DVD) does not.

Answer 1

It is really frustrating when issues like this creep in... all we can do is go methodically through them and try to resolve them as best we can.
Alex offered to look at the project for you if you replace the major assets with still images as place holders. I'll extend the same offer to you if it will help. All I can say is that simulator is not the most accurate of testing stations, and never really has been!
Scripting this is really straight forward as scripting goes, but very daunting if you have never done any before. The thing is that if you have got the stories set up correctly you shouldn't need to script it.
Check a few basics with me...
1) the chapter markers in the track do not have end jumps or menu calls or anything like it set up on them.
2) The menu buttons point to the story container and not the chapter marker within the container
3) the story container has the end jump and menu call set up precisely as you want it to be - none are set to 'same as track'
4) you haven't reused a previous build file
Have you tried quitting and re-starting DVDSP as well? Stranger things have happened...
As for the scripting method - the way you could do this is to create a script for each menu. You can set the first script as the start up item for the disc if you wish, and set it up to read the following:
mov GPRM0, 1
Jump firstmenu
You replace 'firstmenu' with the actual name of the menu - the script editor will only let you choose from menus within your project as you build the script.
Then, each button on the menu goes to the appropriate story, etc. I would imagine that you have got a button which goes to the second menu on there somewhere too... create a script for that button and write:
mov GPRM0, 2
Jump secondmenu
If you have a button on the second menu which returns you to the first, point it to the first script instead of directly to the menu. In this way you can set a unique value relevant to each menu which we can use later, so repeat this sequence for every menu that you have got. Simulator comes in really handy now - you can see the GPRM value change in the info window as you move between the menus to check it is holding the correct value.
Now, to get to the correct button.
When you select a button on a menu the value for that button is lodged into a system register with the nice friendly name of 'SPRM8'. Button 1 on your menu will have a value of 1024, button 2 will be 2048, button 3 will be 3072 and so on in jumps of 1024 each time. Again, you can see this happen in the simulator window, and we can use this information to get back to the right button. It doesn't matter which menu you are on, button 1 will always lodge 1024 into SPRM8...
SO, let's put that together and see what happens.
When you press the 'menu' button on the remote you need to go to a script, so set the menu call in the property inspector to go to the following script (call it what you like... script 23 would be logical, but not too user friendly!)
mov GPRM1, SPRM8
div GPRM1, 1024
Jump firstmenu [GPRM1] If(GPRM0 = 1)
Jump secondmenu [GPRM1] If(GPRM0 = 2)
Jump thirdmenu [GPRM1] If(GPRM0 = 3)
and so on.
What this script is doing is getting the number from SPRM8 and converting it to a usable number (div by 1024), but storing the value into a second register (GPRM1). Then you get the jump statements but the square brackets are GPRM based button jumps - these take you to the button with the value that is stored in the GPRM within the brackets. The final part of the line is the conditional statement - you ONLY jump to the first menu (and button) IF the value in GPRM0 is for that menu. If it isn't you go on to the second line and jump to that menu instead IF the value in GPRM0 is for the second menu...etc. You carry on through the lines until one is true, and that jump takes place - all others are ignored.
Now - that's a really long winded explanation! Sorry about that... it's actually easier to do than to explain.
There are other ways to do this, too. Some are longer again, and others are more confusing (but probably shorter). This method seems a happy medium to me