xgd3 layer breaks

HomeForumsGeneral Discussionxgd3 layer breaks

This topic has 3 voices, contains 6 replies, and was last updated by avatar Sammyboy 1085 days ago.

Viewing 7 posts - 1 through 7 (of 7 total)
Author Posts
Author Posts
2011-09-30 at 05:14PM UTC #1380
avatar
Arianit

The actual layerbreak for XGD3 ISOs is 2133520. However, when burning
XGD3 ISOs to regular DVD+R DL, ImgBurn will automatically reposition/
limit the layerbreak to 2086912 in accordance with the disc’s maximum
Layer 0 data zone capacity (2,086,912 [LBA: 0 - 2086911]). The LT-MAX
feature in LT+ v2.0 will compensate for this and allow you to play
XGD3 backups with this wrong layerbreak, and therefore wrong game
partition data PSN locations.

also this is how we burn them

INSTRUCTIONS FOR BURNING XGD3 BACKUPS WITH IMGBURN

We recommended that you use the latest version of ImgBurn (v2.5.5.0
at the time of writing, downloadable at
http://www.imgburn.com/index.php?act=download). Older versions may
handle this process differently and/or give a different set of
errors.

Although it is set by default in ImgBurn, please ensure that under
Tools > Settings > Write, you have “Layer Break (For DL Media)” set
to “Calculate Optimal”.

Please ensure that the layerbreak is set as 2133520 in the .dvd file.
If you already have the XGD2 (or other) layerbreak value set in
ImgBurn, the .dvd of the XGD3 ISO will override that setting and use
the proper layerbreak.

As mentioned above, ImgBurn will automatically reposition/limit the
layerbreak to 2086912 when burning to regular DVD+R DL discs.

Please see the included imgburn-xgd3-errors.png image for screenshots
of the errors you’ll encounter in ImgBurn and what to click on in
each dialog that pops up.

Step by Step:

1. Choose “Write image file to disc”, and after loading the .dvd
file, click “Write”.

2. ImgBurn will pop up a notice saying that there is not enough
space on the disc to burn the image, and asks if you would like to
continue anyway. Click “Yes”.

3. Another message might pop up saying that optimal layerbreak
position exceeds L0 capacity. Click “Yes”.

4. An error will then pop up noting that “Set L0 Data Zone
Capacity Failed”. Click “Continue”.

5. The image will begin writing to the disc.

6. Nearing the end of the write process, ImgBurn will pop up an
error at around 97% or 98% (this is what we want — it’s
intentional!). Click “Cancel”.

7. A notice will then pop up asking if you would like ImgBurn to
try and perform the “‘Close Track/Session/Disc’ functions”. Click
“Yes”.

8. Let the disc finalize, and you’re done!

:D

  • This reply was modified 1085 days ago by avatar Arianit.
2011-09-30 at 06:22PM UTC #1384
avatar
Sammyboy

Thanks much for this. In the layer break I had “user specified” with 1913760. When I chose “optimal”, 1913760 can still be seen in box opposite “sectors in LO. . Should I still leave on optimal and not worry about it. Should I go back to user specified.

2011-09-30 at 11:09PM UTC #1410
avatar
Sammyboy

Is it still OK to let disc “cycle and verify” ?
Thanks.

2011-10-01 at 12:29AM UTC #1418
avatar
Bloodwing25

people have to remember. THIS still does not patch the game for AP2.5 checks, and it also doesnt work till LT 2.0 gets released. STILL its amazing news!

2011-10-01 at 12:30AM UTC #1419
avatar
Bloodwing25

by the way sammyboy, verifying is a waste of time as long as u do everything else ur suppose to

2011-10-01 at 12:53AM UTC #1424
avatar
Sammyboy

Kinda thought verifying was not needed when everything goes well but better to ask when not sure. Following” burn instructions” to see if I screw it up. I am not a “live” player. Just campaign so not as anxious as some others. If you have any advise on 1st question after your post, feel free to pass along. Thanks for the help. Always appreciated.

2011-10-01 at 02:55AM UTC #1436
avatar
Sammyboy

Followed NFO burn directions. Did what said to do when errors pop up. Finalized disc. Looked exactly like imgburn-xgd3-errors screenshots. So maybe I done good.

:smile:

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.