Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Poll

After experimenting with the options, how is 40d13? Problems only count if the defaults don't work.

Faster than 40d, no problems
- 42 (26.1%)
Faster than 40d, problems
- 72 (44.7%)
No slower than 40d, no problems
- 14 (8.7%)
No slower than 40d, problems
- 16 (9.9%)
Slower than 40d, no problems
- 2 (1.2%)
Slower than 40d, problems
- 3 (1.9%)
Doesn't work (please explain)
- 12 (7.5%)

Total Members Voted: 160


Pages: 1 ... 13 14 [15] 16 17 ... 147

Author Topic: FotF: Help test the output code for the next version of DF (40d13)  (Read 376608 times)

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #210 on: December 25, 2008, 01:18:20 pm »

Got it, I think. It needs teh VC90 *and* VC80 DLLs.

Try downloading and unpacking http://brage.info/~svein/win32_libs.rar into your new DF directory. That should do it. I hope.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Deto

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #211 on: December 25, 2008, 01:24:05 pm »

The new DF doesn't even run for me. On running the .exe, I get an error prompt telling me the application failed to start because it's configured improperly.

I tried downloading a fresh version of the package, and got the same results.

Do you have visual c runtime libraries? If not, installing it might help :)

http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en
Logged

darksaiyan

  • Bay Watcher
  • Livin' with the dwarves since 2007
    • View Profile
    • The Game Reviews Database
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #212 on: December 25, 2008, 01:28:40 pm »

Apparently, pressing space during the intro sequence before creating a world crashes the game for me. Also, you can't press more than one button at once.
Logged

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #213 on: December 25, 2008, 01:34:43 pm »

Unfortunately, there was no way to test multiple simultaneous key-hits on BC. I'm looking into it.

I did notice the MSVCRT dependency, and have added it to my library .rar. If anyone's problems are fixed by this, please try removing DLLs until it fails again, to find out which ones are actually necessary.

The intro (and fullscreen-toggling) crash are in the process of being fixed; that's up to Toady now.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

xylo

  • Escaped Lunatic
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #214 on: December 25, 2008, 01:40:55 pm »

Doesn't run for me.   On running I get "FATAL ERROR: Main index file missing/corrupted.  The file "index" must be in the "data" folder.  Make sure DF decompressed into its folders properly.".  I've verified that the index file is indeed there and dated today.  Also tried a completely clean folder with the same results.  

If I replace the index file with the one from .40d it starts to run and I hear the intro sound etc, but the screen is black.  There will be an occasional block of color but 99% of the time it's just black with no output.

Vista x64
GeForce 8800 GTS (driver version 180.48)

[e] redownloading the package seems to have fixed the problem.  Dunno why.
« Last Edit: December 25, 2008, 01:57:47 pm by xylo »
Logged

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #215 on: December 25, 2008, 01:51:37 pm »

I've seen that happen if the current working directory is wrong, not otherwise. It shouldn't hapen if you're double-clicking directly on dwarfort.exe, under any circumstances.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Udib Gasolbomrek

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #216 on: December 25, 2008, 02:06:20 pm »

@Baughn:

Hey, I've installed darcs, but am having trouble with the repository.  My version is 1.0.9, the last supported for the PPC.

Quote
~/prj/battle_champs>darcs get http://brage.info/~repo_df/ .               [13:58:26]
Invalid repository:  http://brage.info/~repo_df

darcs failed:  Failed to download URL http://brage.info/~repo_df/_darcs/inventory : HTTP error (404?)
~/prj/battle_champs>           

Haven't found relevant advice in TFM.  I notice that your repository has a directory of multiple inventories, but don't what darcs is supposed to be doing at that point.

Important to note that I've also had 404 problems with a HTTP file downloader.  Could this be a web browser client ID string issue with your server?

Logged

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #217 on: December 25, 2008, 02:08:59 pm »

Sorry.. only darcs-2 and above will work.

You could download it with wget -m instead, I guess
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Ostsol

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #218 on: December 25, 2008, 02:42:02 pm »

Am I the only one trying to run this on 64-bit Ubuntu? :) It didn't work, initially, because Ubuntu's ia32-libs package does not include lidSDL-image.  Extracting it from the 32 bit version of that library into the game's libs directory solved that problem, though.

Any chance that we'll see a 64-bit Linux version of DF?

Other nitpicks: every file seems to be flagged as executable.  I'm sure that this is minor, but it's unnecessary. . .

EDIT: I just found that having a grid size other than the standard causes a seg-fault after the intro movie. . .

Code: [Select]
Using OpenGL output path with client-side arrays
Ideal catalog size: 384x368
Assumptions broken!
Segmentation fault
« Last Edit: December 25, 2008, 02:59:26 pm by Ostsol »
Logged
Ostsol

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #219 on: December 25, 2008, 02:50:08 pm »

Hmm, let me think..

No.

There are *way* too many 32-bitisms in the source, and no doubt a ton more in DF proper; there's no way it'll work.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #220 on: December 25, 2008, 02:51:25 pm »

Oh, and it should be perfectly possible to compile darcs-2 on ppc yourself. Probably.

It's haskell, after all; high-level code. It's *hard* to make it platform-dependent.
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

puke

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #221 on: December 25, 2008, 03:00:30 pm »

does not seem to run on vista, i get a message that the "side by side" configuration is incorrect.

Quote
Activation context generation failed for "C:\Users\lmiller\Desktop\df 28.181.40d2\Dwarf Fortress.exe".Error in manifest or policy file "C:\Users\lmiller\Desktop\df 28.181.40d2\Microsoft.VC90.CRT.MANIFEST" on line 4. Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". Definition is Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.1". Please use sxstrace.exe for detailed diagnosis.
Logged

Ostsol

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #222 on: December 25, 2008, 03:02:08 pm »

Ah, that's too bad. . .  It wouldn't be the first game to suffer such a problem, though.  I've been wanting to play IVAN in Linux for a while, but it's also too 32-bitty to be converted easily.
Logged
Ostsol

Baughn

  • Noble Phantasm
  • The Haruhiist
  • Hiss
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #223 on: December 25, 2008, 03:04:59 pm »

Please use sxstrace for a detailed diagnosis. ;)

The appropriate command line is.. well, I don't really know, not having Vista, but there's an article on it at http://blogs.msdn.com/junfeng/archive/2006/04/14/576314.aspx - it would be really helpful.  :D
Logged
C++ makes baby Cthulhu weep. Why settle for the lesser horror?

puke

  • Bay Watcher
    • View Profile
Re: Future of the fort: Help test the output code for the next version of DF
« Reply #224 on: December 25, 2008, 03:13:02 pm »

here you go:

Code: [Select]
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = x86
CultureFallBacks = en-US;en
ManifestPath = C:\Users\lmiller\Desktop\df 28.181.40d2\Dwarf Fortress.exe
AssemblyDirectory = C:\Users\lmiller\Desktop\df 28.181.40d2\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\Users\lmiller\Desktop\df 28.181.40d2\Dwarf Fortress.exe.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"
INFO: Resolving reference Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.CRT\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\Users\lmiller\Desktop\df 28.181.40d2\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\Users\lmiller\Desktop\df 28.181.40d2\Microsoft.VC90.CRT.MANIFEST.
INFO: Manifest found at C:\Users\lmiller\Desktop\df 28.181.40d2\Microsoft.VC90.CRT.MANIFEST.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC90.CRT.mui,language="*",processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.CRT.mui\9.0.21022.8_en-US_1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.mui.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.CRT.mui\9.0.21022.8_en_1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.mui.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Find publisher policy at C:\Windows\WinSxS\manifests\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_9193a620671dde41.manifest
INFO: Publisher Policy redirected assembly version.
INFO: Post policy assembly identity is Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
INFO: Begin assembly probing.
INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8.manifest.
INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8.manifest.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC80.CRT.mui\8.0.50727.762_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC80.CRT.mui\8.0.50727.762_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Parsing Manifest File C:\Users\lmiller\Desktop\df 28.181.40d2\Microsoft.VC90.CRT.MANIFEST.
INFO: Manifest Definition Identity is Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.1".
ERROR: Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". Definition is Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.1".
ERROR: Activation Context generation failed.
End Activation Context Generation.

Logged
Pages: 1 ... 13 14 [15] 16 17 ... 147