Page 1 of 1

Patch 1.3.21 - August 2015

Posted: Sun Aug 23, 2015 10:07 pm
by Spiky Caterpillar
Plot fixes:
* Elodie no longer writes a letter to Charlotte (when she suspects Charlotte's healing powers might have something to do with Lumen ancestry) if Charlotte's already in the castle.
* Delaying your marriage to Banion now shows up properly in the epilogue.
* Slight rewording of Internal Affairs 50 text.

Video tweaks:
* There's now a 'Snap to 1024x600' button, so you can fix the window size if you want everything pixel-perfect. (The code has been there since forever, but the button wasn't being displayed.)
* A system/image cursor toggle has been added. In image cursor mode, you get the magic wand from the prefs screen as your cursor. This is a hack to help LPers - normally, LLtQ will skip redrawing frames when possible to save CPU time and battery life. However, several video recording programs don't work well at low/variable framerates (or work just fine but ignore the cursor because that's drawn by the OS rather than the game.). Using an image cursor forces more frequent redraws, as every mouse movement will then trigger redraw.

Behind the scenes:
* Some improvements to the updater have been pulled in from Black Closet. They'll never be seen unless we update the .rpa file some year.

Translation fixes (Go to http://spikycaterpillar.com/long_live_t ... anslation/ for the translation archive)
* moodbg.png now translatable.
+ Layered graphics for the mood display and the menu buttons now included in the translation archive.
+ Some missing strings in translations (dogs 10, touchscreen map) fixed.
* Should no longer crash when it encounters tags in translations. This may work around a crash bug triggered by at least some versions of the Korean translation.

Re: 1.3.21 in beta

Posted: Sat Aug 29, 2015 1:42 am
by hanako
(Shall I assume that all seems to be working as desired?)

Re: 1.3.21 in beta

Posted: Sat Aug 29, 2015 2:39 am
by Mir
Banion's two delayed marriage epilogues and Internal Affairs 50 are both displaying correctly and I'm having too much fun with the new cursor.

Re: 1.3.21 in beta

Posted: Sat Aug 29, 2015 2:54 am
by hanako
Banion should have three delayed marriage epilogues, actually. :)

One of which is identical to the original ballet-leotard marriage but put in a different position in the epilogue, and two that aren't.

Re: 1.3.21 in beta

Posted: Sat Aug 29, 2015 3:27 am
by Mir
Ah. So he does. (It's working.)

Re: 1.3.21 in beta

Posted: Sat Aug 29, 2015 8:09 pm
by Darksilverhawk
Not a direct cause of the patch, but I'm having issues with the game not fullscreening properly on Windows 10, 1280x800 native screen resolution. if I try to fullscreen, I'm getting black bars blocking out the top and bottom 200ish pixels. Anything in those pixels is unclickable.

Re: 1.3.21 in beta

Posted: Sat Aug 29, 2015 11:27 pm
by hanako
Does changing display modes with video preferences help? I don't know much about windows 10.

Re: Patch 1.3.21 - August 2015

Posted: Sun Aug 30, 2015 3:59 am
by Darksilverhawk
Switching to OpenGL helps, kind of, but the game is now trying to run at way too large a resolution than fits on the screen. This might be a Windows 10 thing, though, as other games have had this problem on my system as well.

Re: Patch 1.3.21 - August 2015

Posted: Sun Aug 30, 2015 11:33 am
by hanako
Sorry that my help on this issue is blatantly flailing around blindly. I don't actually know, I'm just suggesting areas to look in. :)

Check for updated drivers on your graphics card? Because yeah if you're seeing strange results on multiple games, this implies to me that your graphics card is not happy with the current setup somehow.

Re: Patch 1.3.21 - August 2015

Posted: Sun Aug 30, 2015 6:45 pm
by Darksilverhawk
Yeah, it seems to be a driver issue. I should have thought of that first.

Re: 1.3.21 in beta

Posted: Tue Sep 15, 2015 12:52 pm
by Ariel Schnee
Darksilverhawk wrote:Not a direct cause of the patch, but I'm having issues with the game not fullscreening properly on Windows 10, 1280x800 native screen resolution. if I try to fullscreen, I'm getting black bars blocking out the top and bottom 200ish pixels. Anything in those pixels is unclickable.
That's because 10 is crap.

You should stick with with XP instead.

Or 7 in XP mode.