Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Random_Dragon]

Gorlaks! Yeah!!
Thanks Toady.

Good thing that you mentioned it, prompting me to comment and tag the issue. o3o

[jecowa]

I always thought that Gorlaks must be too short to properly manipulate the door handles.

[Telgin]

If we were using the 64 bit beta release of 43.04, can we migrate saves over with mild to no issues?

I haven't noticed any problems yet at least, so I believe so.

[Random_Dragon]

I always thought that Gorlaks must be too short to properly manipulate the door handles.

And I will eat the next person to suggest that. :V

[Random_Dragon]

I am however somewhat irked that Toady doesn't include the 32-bit version on the same page as the other versions. Eh. Also, all of a sudden we got a fuckton of shiny new DLL files.

[jecowa]

Most people don't know what 64-bit and 32-bit are. Or the difference between an SDL and Legacy version. I like the change. This will also allow him to get a better idea of how many are still requiring 32-bit versions.

[Random_Dragon]

By way of seeing how many people bitch about it? ;w;

[Boltgun]

Good job, 64 bits looked surprisingly fast to release. All the pointers are pretty happy.

Spoiler: obligatory (click to show/hide)

DWARF FORTRESS SIXTY FOOOOOOOOOOOOOOOOOOOOOOOOR



(sorry)

[Thief^]

There are extra dlls in the release which aren't needed:

The msvc*80 and *100 dlls are from older versions of visual studio (msvc*140 is the newest). You probably don't need the "Microsoft.VC80.CRT.MANIFEST" either, for the same reason.

You also have two versions of libtiff and libpng included. In addition, do you actually support jpeg and webm image formats? If not, you don't need those dlls either I don't think.

[Random_Dragon]

I noticed that. The 32 bit version has a fuckton of DLLs not included in prior versions, and I have no idea whether they were ever required.

[Thief^]

The api-* DLLs are all for compatibility with Windows 7 and earlier I believe. They implement "API Sets", where certain APIs are divorced from exactly which DLL implements them, allowing easier updating/patching for MS in future. This was introduced in Windows 8, Windows 7 and XP need these "shim" DLLs to emulate API Sets as those OSs don't have built-in support.

On the plus side, because they are just shims, they are all tiny.

[Random_Dragon]

Ah, my potato computer strikes again. Nevermind the fact that just updating my redistributable fixed all problems I had last version, so this still sounds unnecessary for Windows 7.

[TheHossofMoss]

I've merged my last fortress with this version (it was from 43.04). I've noticed nothing strange so far. Do you people think that might cause problems down the road or should I be fine?

[ChaotikDwarf]

The api-* DLLs are all for compatibility with Windows 7 and earlier I believe. They implement "API Sets", where certain APIs are divorced from exactly which DLL implements them, allowing easier updating/patching for MS in future. This was introduced in Windows 8, Windows 7 and XP need these "shim" DLLs to emulate API Sets as those OSs don't have built-in support.

On the plus side, because they are just shims, they are all tiny.

I seriously doubt it, since i use vs2015 currently and i don't need all that crap with any of my executables.
Also , statically linking can often give a nice boost to perf as it allows more optimizations.

[Aklyon]

So why all the extra bits then?