Langrisser Projects

As many as 1,645 users have downloaded the Der Langrisser translation from this website; 2,229 have downloaded it from ROMHacking.net; an unknown quantity have downloaded it from Clouds of El Sallia.

That’s a lot of downloads.

But the truly amazing thing is this: ten people have downloaded the QNX patcher.

In addition to the known bug in ZSNES and SNES9x that cause Der Langrisser to periodically lock up and crash, mil from the Fantasy Anime forums has verified that the bug also occurs in SNEeSe. Therefore, we do not recommend playing Der Langrisser in SNEeSe, either.

This leaves bsnes and SNESGT as the only verified emulators capable of playing Der Langrisser correctly. As an aside, Super Sleuth is completely unverified, and lacks both sound support and speed throttling, but may still work if you’re willing to play that way.

We are still accepting bug reports at this time.

Our current plans are to develop a new patching format. We expect this to take 1 - 3 months to complete. Once finished, we will be releasing a new patch in this format. This will be the final release, at which time we will no longer accept any bug reports.

If you see a bug and want it fixed, you absolutely must report it as soon as possible. We do not intend to continue to support Der Langrisser for the rest of our lives. We have over four hundred downloads of our patch thus far, so there is absolutely no reason any bug should remain uncovered within the next few months.

We are accepting reports on the following issues at this time:

• Programming errors
• Wrong portrait errors, eg dialogue shows Aaron but portrait shows Cherie. We may or may not fix these at our discretion. They are all bugs from the Japanese game, and not from our translation.
• Script errors, such as a character speaking in the wrong person, eg “You have failed.” when the text should clearly state “I have failed.” — the context should make it clear when this is an error.
• Script errors, such as a window with only a single word, formatting errors, typos, etc

We are not accepting reports on these issues:

• Graphical glitches on character sprites, eg Bernhardt turning into Egbert or glitches after being killed by a Vampire Lord — these are bugs in the Japanese game that is due to WRAM corruption. We do not have the resources to reprogram half of the game engine to fix this. The bug is not the fault of our translation patch.
• Problems in the load screen secret menu (L, R, L, R, Select, A). There are multiple bugs here, and all of them are from the Japanese game. Notably, some sound effects do not play, and many options in the Battle Test menu will cause the game to show garbled backgrounds, play incorrect sounds, and possibly even crash the game. There is a reason this feature was not enabled in the Japanese release. We chose to release it as we knew many people would enjoy seeing it anyway. Again, none of these were caused by our translation.
• Sound cutoff at the end of the introduction loop by ~3 seconds. This is due to the extended length of dialogue text used by the English translation. There is little we can do here.
• Dark Princess - Dark Princess overflows the 8×8 Name - Class line by two pixels. It is still perfectly readable, and does not cause any glitches. The text is not even clipped. Our only other option is to shorten this line, but there is no reason to. It fits perfectly fine.
• Personal opinions on how something should be translated. The script has been meticulously edited for several years. We do not care if you are upset with our use of profanity, localizations, colloquialisms, etc
• Odd script messages when a character is killed. This is usually due to killing a character on the first attack, and is not a bug.

If you would like to submit a bug report, you may either submit it here, or on the Clouds of El Sallia forum. We will not accept bugs from anywhere else.

When submitting a bug, you must include all relevant information. We need the exact text spoken, a detailed reason of what is wrong and why you believe it is wrong, and how to reach this bug. If it is a programming bug, you will need to post a save RAM (.srm) file, and not a save state (.zsN, .s9N, etc). You can make the needed save RAM by choosing the “Save” option from the game menu immediately before the bug. Exit the emulator to be sure your save RAM was updated before mailing it to us.

We thank you in advance for any bug submissions, and apologize for any bugs you encounter while playing. It is inevitable that some issues will have slipped past us during beta testing.

Today, we released a brand new patcher version that supports QNX Neutrino 6.2.1. The binary is compiled for x86 architecture. There were just too many errors on ARM and MIPS to take the time to resolve. Now all five QNX users can enjoy Der Langrisser too!

We’ve also released a small “press kit” which contains 32 screenshots from the game and some high-resolution TIFF and PSD images for anyone creating a derivative work. The archive is public domain, so do with it as you wish.

Today, we rolled out patch version 1.01. We have updated all the patchers, and also released a new DOS port. Sadly, we are still waiting on an OS X PowerPC build.

This update is critical! There is one scenario that was not even playable because of an error in the script file that no one ever caught. It also make some light fixes to the introduction, and fixes one typo in one of the possible endings for Scott.

You will need to apply this patch to a clean ROM file. It cannot be applied over your already patched Der Langrisser ROM. Using a current savestate may work in the new patch, but it is much safer to continue with an in-game save.

During play, press START and select Save from the menu. Select “Yes.” Then exit your emulator or power off your console. Name your new patched ROM to the same filename as your old one, and delete the old one. When you start up, simply chose to Load the first scenario save slot.

400 downloads of the Windows patcher
14 downloads of the Linux patcher
10 downloads of the OS X patcher

128 downloads of the printable manual
125 downloads of the high resolution manual
46 downloads of the regular manual (retardation?)

Der traffik total is: 1,81GB

Go server, go!

(These numbers only account for local downloads. Not downloads from our mirror sites.)

I’ve replaced all the manuals on this site with new prints. These prints correct the “Page 14″ typo, as well as that last minute “Arch Mage” to “Archmage” fix. This is the last time I will correct the manuals.

I spent a lot of time fine tuning the PDF settings, so if you are using Adobe Acrobat Read 8.0 (maybe 7.0 too), you should get a nice surprise. The PDFs are fully bookmarked, and clicking a page name will jump you to the target page. They are also configured to open at Actual Size instead of Best Fit, are flagged as English so blind Der Langrisser players like aerdan can read them with screen reader software and a bunch of pageflow options have been tweaked too.

If you are using Acrobat 8, it is better to download the printable manual. It will look the same as the high resolution one for you, but will have better page jumping due to its split nature. Users of open source PDF readers should stick with the default file or the high resolution one.

For anyone curious about the manual, it was designed in QuarkXpress 7.0 for PC, the best layout software around: period. No matter what Adobe InDesign people will insist, Quark will always be their daddy.

The manual was printed as 4,000dpi output onto a 127mmx127mm paper. The color feed is Composite RGB rather than CMYK, because these are more vibrant for screen readers. The color frequency went out at 200, which means zero angle on the yellow channel. Pictures were fed as Binary using full-resolution TIFFs. All fonts were optimized and embedded, and transparency flattening occurred at 600dpi.

The manual is primarily set in Bitstream Vera Sans and Serif–I selected these fonts because I had never laid anything out with free fonts, and I wanted a challenge. The black stripe Der Langrisser text is set in Georgia. I think nine style sheets were used for the whole manual.

As for the PDFs themselves, they were generated used Acrobat Distiller 8.0.0 for Windows XP, which creates using PScript5 Version 5.2. The high resolution and print manuals are printed as a High Quality Print PDF, and the pack-in manual is Standard quality.

Hi, if you get to the harbor battle scenario where you fight monsters, not Imelda, do not win before the boat leaves. You will need to lose and let the boat escape.

Why?

Ask our Light Path beta testers Hope you will all be able to enjoy that version of the path when we are forced to do a 1.01 patch.

Things never quite go the way we plan. It turns out the OS X patcher only works on Intel architecture Macs. We are waiting for MaDMaLKaV to get online since he has volunteerd to make one for PowerPC users. Because of this hiccup, the archive has been renamed to reflect its Intel-only nature.

Mirrors for all patches are available via Clouds of El Sallia’s Der Langrisser sub-page.

Lastly, sorry about the print-layout manual being broken. That’s my fault. While uploading it, I ran out of disk space. Since it never threw a disk space error till the next file, I assumed everything went up without any trouble. Nope. The file has been re-uploaded. This should please all the pirates who are getting ready to flash this translation to a cartridge and sell it on eBay under the false pretense that it is a newly discovered beta cartridge.

Yes, I know there are two errors in the manual. The class change charts still show “Arch Mage” when a last minute change led to switching this to “Archmage.” Also, one of the references to a page number is wrong. Of course, when you compare this to the shitloads of errors in commercially-made, professional instruction manuals, they are quite minor. If it didn’t have at least one or two errors, it would probably seem less like a professional game manual

Check the Downloads page.

I am too tired to make a link to it. If you can’t find it, try looking at the top of the page.