Game loaded different than selected

Issue #23 resolved
Former user created an issue

Good Afternoon -

I've been using xkeyBrew here and there for a couple of weeks now, but have a consistant issue which has not changed no matter which themes i use:

When the xKeyBrew DVD menu is loaded in my XBOX 360, I select the game I want to play, hit the Home button, exit to dashboard, eject disc, then allow it to close and load. Unfortunately, the game loaded is not the one I selected. The good news is that it consistantly loads the games indexed prior to the one selected.

Example: In the xKeyBrew app, I can preview the DVD menu as follows: - Index 0 - Game 1 - Index 1 - Game 2 - Index 2 - Game 3 - Index 3 - Game 4

When loading from the XBOX, itself, it seems that the structure is: - Index 0 - Don't know - haven't actually tried it - Index 1 - Game 1 - Index 2 - Game 2 - Index 3 - Game 3

Therefore games selected to load always load the previously indexed one.

When build the menu in xKeyBrew, default options are selected. Below are my system specs as well as a log file from a build I just did attached.

System Specs - Intel i7 3770k / 16gb RAM - Windows 7 x64 (Fully Patched) - Java 7 Update 45 (x86 & x64) - xKeyBew 1.7.1 - Custom Theme used which was made from the City theme. Issue occurs no matter theme used, though - Game ISOs are in a folder named "games" in root of external USB 3.0 1tb Hard Drive which is formatted NTFS. The only other files besides ISOs are the cover images for each. There is a seperate folder in the "games" folder named "unpatched" which holds any ISOs not verified by ABGX yet.

Note: I have been using 1.7 until visiting the site today. Therefore, I ran the build with 1.7.1 which I haven't tested yet. I went ahead and posted as the change log didn't mention an issue specific to this.

I removed the first part of the log file simply for privacy reasons.

Thank You!

Comments (4)

  1. Ben Kellermann

    Just my luck...

    Just tested build made from 1.7.1 and indexing seems to be resolved. Knew if I posted before testing this would happen.

    Thank You

  2. 巴蒂斯Badisi repo owner

    You are right, this has been fixed in 1.7.1.
    Issue #22 was different but related to the same problem (a regression introduced in 1.7)
    I have updated the change log to mentioned this issue too.
    Thanks

  3. Log in to comment