woot

[Spicedstoner]

Patching

[The Derr Man]

I assume the patch is just bug patching and optimization. But it seems to have a DirectX 11 exe now. It's not functioning yet even with steam_api64.dll in the folder.

I already 100% the game, I guess I was lucky to not get any glitches. Only problems I had were crashes to desktop. Can't wait until part 3.

[The Derr Man]

Originally posted by ShiningDragon:

Does the patch prevent the Hobbit now from saving the pc config files to the root of my second harddive "\Warner Bros. Interactive Entertainment\LEGO The Hobbit" ?

Oh just checked that and there is now a folder in 'AppData\Roaming\Warner Bros. Interactive Entertainment\LEGO The Hobbit'.

I guess that is why settings were reset.

[ShiningDragon]

Hooray, great. :)

[Savok]

Originally posted by ShiningDragon:

Does the patch prevent the Hobbit now from saving the pc config files to the root of my second harddive "\Warner Bros. Interactive Entertainment\LEGO The Hobbit" ?

Seriously? They stuck it in the ♥♥♥♥♥♥♥♥ root?

And ♥♥♥♥♥♥♥♥♥, so they did. Are they unlearning how to make games? This isn't new to them. Still I guess it stands to reason the game's as competent as the movies.

[BushwalkerSP]

This is a strange patch and looks incomplete, because (as mentioned above) DirectX 11 is not working. Or they expect you to re-install the game. Either way, without steam_api64.dll that update is probably useless.

[The Derr Man]

Originally posted by Savok:

Originally posted by ShiningDragon:

Does the patch prevent the Hobbit now from saving the pc config files to the root of my second harddive "\Warner Bros. Interactive Entertainment\LEGO The Hobbit" ?

Seriously? They stuck it in the ♥♥♥♥♥♥♥♥ root?

And ♥♥♥♥♥♥♥♥♥, so they did. Are they unlearning how to make games? This isn't new to them. Still I guess it stands to reason the game's as competent as the movies.

I assume it was just an oversight, probably set the save using %homedrive% during development and then just forgot to change it to %appdata%. But at least it is fixed and you can delete the folders in the root.

[Grim]

There's also 4 DLC files in the game directory. They just say "DLC" in each.

[The Derr Man]

Originally posted by Plingbrix:

There's also 4 DLC files in the game directory. They just say "DLC" in each.

Yeah probably the 3 packs that are already on consoles, and possibly a new one or part 3...

[Alktor]

Does patch add DLC or not ? Because when I see the link given by Kreker they are DLC 1, 2, 3...

[Nomad Time Lord]

They're not going to release the third book this long before the movie, I don't know why anyone's speculating that. The size of the patch doesn't mean much these days; I've seen 5gb patches for three minor bug-fixes and no content change, and 3mb patches that had over 30 fixes.

[Chaisy]

Any tips for someone that has never run the game for the first time? Based on the folder changes should it setup correctly on the first start up? Or should I delete specific folders and verify cache or just delete and reinstall entire game? TIA :)

[Doctor Hades]

The V-Sync setting in the game STILL does NOT save! How many LEGO games have Traveler's Tales made now? Over a dozen by my reckoning and almost all of them saved the V-Sync setting correctly except for these new games. Seriously, how could they break something so simple...and then not take the opportunity to fix it at all in a 1.1 GB patch? lol

Also, what is the point of the DX11 executable if it does work (missing Steam_API64.dll)? Do the developers not test these patches on Steam before they upload them?

[Doctor Hades]

I actually got the DX11 executable to start loading and confirmed with Afterburner's OSD that it *IS* using DX11 and not DX9 by coping the Steam_API64.dll from the Van Helsing II folder. However, there were no loading screens and the game eventually exited back to the desktop. So it does look as if a custom Steam_API64.dll is the only thing preventing the DX11 version from working.

[BushwalkerSP]

Originally posted by Doctor Hades:

The V-Sync setting in the game STILL does NOT save! How many LEGO games have Traveler's Tales made now? Over a dozen by my reckoning and almost all of them saved the V-Sync setting correctly except for these new games. Seriously, how could they break something so simple...and then not take the opportunity to fix it at all in a 1.1 GB patch? lol

Also, what is the point of the DX11 executable if it does work (missing Steam_API64.dll)? Do the developers not test these patches on Steam before they upload them?

Yeah, it's a drag, I know. You need to change IgnoreVendorPresets to 1 in pcconfig file in order to keep V-sync settings.

[Septarius]

Originally posted by Doctor Hades:

I actually got the DX11 executable to start loading and confirmed with Afterburner's OSD that it *IS* using DX11 and not DX9 by coping the Steam_API64.dll from the Van Helsing II folder. However, there were no loading screens and the game eventually exited back to the desktop. So it does look as if a custom Steam_API64.dll is the only thing preventing the DX11 version from working.

I copied the steam_api64.dll from Centration (I have the dev branch) it is Steamworks SDK 1.29 signed by Valve on April 21st. From what I have found this file shouldn't be specific to any one game as its the Steamworks API. Just have to have the version that is equal to or close to the version the game wants.
The steam_api.dll was signed March 15, 2012 so if the 32 bit SDK is the same one they used for 64 bit, there is a chance any steam_api64.dll newer than that could work.

Other games I have that have a steam_api64.dll are: Trine 2, 3DMark, Spiral Knights, Portal 2. In declining likely hood that they could work.

I was able to play through the first level just fine, YMMV. Of course backup all save games before trying this. No warranty provided, etc.

Hopefully they just push a new patch out with the file they missed.