Recent Posts

Pages: [1] 2 3 ... 10
1
Bloodlines Modding / Re: Bloodlines SDK
« Last post by Uradamus on June 20, 2017, 10:18:52 PM »
I'm on the latest 64-bit Manjaro Linux (w/ the Cinnamon desktop) and using Wine-staging 2.9 with a 32-bit prefix.
2
Bloodlines Modding / Re: Bloodlines SDK
« Last post by Wesp5 on June 20, 2017, 04:52:52 PM »
Hm... Okay, please tell me what version of OS distrib and Wine you're using, and I'll try to reproduce your issue when I have a time.

Maybe the .bat file needs a special command to not auto-close on ending?
3
Bloodlines Modding / Re: Bloodlines SDK
« Last post by Psycho-A on June 20, 2017, 04:42:37 PM »
Hm... Okay, please tell me what version of OS distrib and Wine you're using, and I'll try to reproduce your issue when I have a time.
4
Maybe some mod in the future will "add" more lore behind it - the possibility of having conversation with Bruno and perhaps some other characters just to name a few.

This could indeed be done in a "sequel" kind of mod, showing what happens in LA after the incident. The main problem for me though would be the missing voice-overs!

There is an easy way to overcome that: 
Set the story some years away after the power in LA shifted and new players surfaced.
Get amateur or semi-pro voice actors that can reliably mimic some of the old characters or do decent voice acting for existing ones.
5
Bloodlines Modding / Re: Bloodlines SDK
« Last post by Uradamus on June 20, 2017, 01:05:59 PM »
As I said, when I ran the .bat I got the exact same output as when I ran the main exe, no console showed up, and the output in the console I was using to launch things was identical to what you see in the screenshot from the last post, the error dump was idtentical too, so it made no sense to waste time taking and cleaning up a second screenshot when it would have made no difference.

An interesting thing happened when I unpacked a fresh copy of Bloodlines and installed the 96 final UP, the included SDK ran into the same exact error even though it didn't previous to trying to run the version that came with 97 final and the newer SDK builds. So I created a whole new prefix, reinstalled steam and bloodlines, installed the 97 final UP, and then the latest SDK, and ran into the same problem, when I again got rid of Bloodlines, unpacked a fresh copy and went with 96 again, I ran into the same problem again.

BUT, after doing this all over again, fresh prefix, fresh Steam, fresh Bloodlines and this time going with 96 final right form the start, I was able to get the version of the SDK that came with that to run the setup cleanly with no errors, well except when I went to run the unpacker it was looking to the wrong dir and told me I should edit the related config file through the SDK interface.

So one thing this tells me is that the versions of the SDK after what's included with 96 final UP are probably setting something wrong in the registry, that is the only explanation for why the version included with 96 can't run properly after a newer version has been run. When I am trying a new install I just delete the Bloodlines install dir (where the UP and dev tools are installed as well) and unpack a clean unpatched copy I keep an archive of to save me from having to download from Steam again, then apply any patches I need to the fresh install. That process doesn't touch the registry though, so something messed up must be going on in there, since all settings saved within the SDK install dir itself are getting wiped when I replace my Bloodlines install. I had a look around in the registry and other than the Trokia stuff with a section for Hammer settings, I couldn't find anything that seemed related to the SDK. Not sure where they might be buried in there,

Edit: Oh, forgot to mention, the new prefixes only got cmd and vcrun2005/2008/2010 as far as extra stuff installed via winetricks. Without that stuff the SDK doesn't run, just in case any one else came along who wanted to try this stuff out in Wine as well.
6
Bloodlines Modding / Re: Bloodlines SDK
« Last post by Psycho-A on June 20, 2017, 11:12:22 AM »
Quote
I've included the requested screenshot. It's for the main exe, but when I tried to launch the bat I got the exact same output, so it shouldn't really matter. Also, here is the full output from the crash window Wine pops up, should be pretty similar to the one I posted previously.
I asked you for launching by .bat file because it brings up native Windows command line window to be visible so I could see which exactly happens on the troubled launching step. Sadly the screenshot you sent me talks about nothing. Also, have you tried the older SDK builds (you supposed to be working) right now? Maybe it's not the SDK's fault at all, and now you get the same error on any version.
7
Maybe some mod in the future will "add" more lore behind it - the possibility of having conversation with Bruno and perhaps some other characters just to name a few.

This could indeed be done in a "sequel" kind of mod, showing what happens in LA after the incident. The main problem for me though would be the missing voice-overs!
8
Also, back to the topic. ;)
What do you think about Chunk and Arthur or any other minor character (Cal already got here a treatment)? Maybe their roles could be deepened somewhat and enriched with more background elements: there are some scattered clues about them (Arthur for example) but nothing more than their quests or some side information that is really difficult to go on in the long run. Conversation with Trip and Venus could be a bit more detailed; the minor characters in Chinatown (except Wong Ho) are also a potential that was left behind - Mr.Ox and his true nature have been the topic of debate here a lot for example, but that character is not used enough.
One more thing: that Giovanni mission is really always a disappointment when I play: so much wasted potential and/or not used. Maybe some mod in the future will "add" more lore behind it - the possibility of having conversation with Bruno and perhaps some other characters just to name a few.
9
Bloodlines Modding / Re: Bloodlines SDK
« Last post by Uradamus on June 20, 2017, 07:20:32 AM »
The very first time I tried running the SDK that came with the latest UP I think I got the popup telling me that the setup was starting, but as soon as I clicked on the first button to open up the window to chose a dir I got a crash popup from Wine about the divide by zero error. But the initial popup was still there and I was able to hit cancel or whatever to skip manually chosing dirs, and that closed down and the SDK window came up. But any time I tried to click on the option to change game dir I would get the crash popup from Wine again with the same error.

Every single time after that though, including with each SDK update I've tried so far, as soon as I try to launch the SDK I get the the crash popup with the same error as the above instances. I no longer get the initial setup notice popup and the SDK window itself never launches.

I tried to run Start_SDK.bat as suggested (using wineconsole) and that gave the exact same error output as if I were trying to launch from the main exe. I did however decide to give a shot at running sdklauncher.exe and that brings up the main SDK window just fine, so it seems to be a problem somewhere early on with one or more of the bits that try to run before that either with checking the install or running the setup.

I've included the requested screenshot. It's for the main exe, but when I tried to launch the bat I got the exact same output, so it shouldn't really matter. Also, here is the full output from the crash window Wine pops up, should be pretty similar to the one I posted previously.
Code: [Select]
Unhandled exception: divide by zero in 32-bit code (0x7ed1e452).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:7ed1e452 ESP:0033f9c0 EBP:0033fa88 EFLAGS:00010202(  R- --  I   - - - )
 EAX:00000640 EBX:00000492 ECX:00000000 EDX:00000000
 ESI:0033fb7c EDI:0033fa3c
Stack dump:
0x0033f9c0:  001109e8 0033fbd4 0000000d 00000190
0x0033f9d0:  0033f9ec 0033f9fc 7ed26000 001109e8
0x0033f9e0:  00010007 00000000 0033fa88 00000000
0x0033f9f0:  00000000 00000640 00000492 0000004a
0x0033fa00:  00000000 00000000 00000040 00000060
0x0033fa10:  00000000 00000000 00000000 00000000
Backtrace:
=>0 0x7ed1e452 in wineconsole (+0xe452) (0x0033fa88)
  1 0x7ed1f09b in wineconsole (+0xf09a) (0x0033fc68)
  2 0x7ed1f715 WinMain+0x384() in wineconsole (0x0033fd28)
  3 0x7ed143b7 main+0xd6() in wineconsole (0x0033fdc8)
  4 0x7ed1fa64 in wineconsole (+0xfa63) (0x0033fe08)
  5 0x7b461c99 call_process_entry+0x18() in kernel32 (0x0033fe38)
  6 0x7b462d5c in kernel32 (+0x42d5b) (0x0033fe88)
  7 0x7bca51cc call_thread_func_wrapper+0xb() in ntdll (0x0033feb8)
  8 0x7bca843f call_thread_func+0xce() in ntdll (0x0033ffa8)
  9 0x7bca51aa RtlRaiseException+0x21() in ntdll (0x0033ffc8)
  10 0x7bc75b93 call_dll_entry_point+0x432() in ntdll (0x0033ffe8)
  11 0xf759b50d wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000)
  12 0xf759b670 wine_switch_to_stack+0x1f() in libwine.so.1 (0xffc21828)
  13 0x7bc7cd9b LdrInitializeThunk+0x39a() in ntdll (0xffc218a8)
  14 0x7b46950a __wine_kernel_init+0x929() in kernel32 (0xffc22a18)
  15 0x7bc7d99d __wine_process_init+0x15c() in ntdll (0xffc22a88)
  16 0xf759a418 wine_init+0x2d7() in libwine.so.1 (0xffc22ae8)
  17 0x7c000c02 main+0x81() in <wine-loader> (0xffc22f48)
  18 0xf73c8253 __libc_start_main+0xf2() in libc.so.6 (0x00000000)
0x7ed1e452: divl 0x40(%esi),%eax
Modules:
Module Address Debug info Name (49 modules)
ELF 7b400000-7b7eb000 Dwarf           kernel32<elf>
  \-PE 7b420000-7b7eb000 \               kernel32
ELF 7bc00000-7bd24000 Dwarf           ntdll<elf>
  \-PE 7bc40000-7bd24000 \               ntdll
ELF 7c000000-7c004000 Dwarf           <wine-loader>
ELF 7ec8a000-7ed02000 Deferred        advapi32<elf>
  \-PE 7eca0000-7ed02000 \               advapi32
ELF 7ed02000-7ed4d000 Dwarf           wineconsole<elf>
  \-PE 7ed10000-7ed4d000 \               wineconsole
ELF 7ed4d000-7ed60000 Deferred        libnss_files.so.2
ELF 7ef60000-7efbc000 Deferred        libm.so.6
ELF f69ad000-f69b4000 Deferred        libxfixes.so.3
ELF f69b4000-f69bf000 Deferred        libxcursor.so.1
ELF f6a65000-f6a8f000 Deferred        libexpat.so.1
ELF f6a8f000-f6ad9000 Deferred        libfontconfig.so.1
ELF f6ad9000-f6b52000 Deferred        libpcre.so.1
ELF f6b52000-f6c7d000 Deferred        libglib-2.0.so.0
ELF f6c7d000-f6d09000 Deferred        libharfbuzz.so.0
ELF f6d09000-f6d47000 Deferred        libpng16.so.16
ELF f6d47000-f6d58000 Deferred        libbz2.so.1.0
ELF f6d58000-f6d71000 Deferred        libz.so.1
ELF f6d71000-f6e3e000 Deferred        libfreetype.so.6
ELF f6e3e000-f6e51000 Deferred        libxi.so.6
ELF f6e51000-f6e55000 Deferred        libxcomposite.so.1
ELF f6e55000-f6e62000 Deferred        libxrandr.so.2
ELF f6e62000-f6e6e000 Deferred        libxrender.so.1
ELF f6e6e000-f6e75000 Deferred        libxxf86vm.so.1
ELF f6e75000-f6e79000 Deferred        libxinerama.so.1
ELF f6e79000-f6e80000 Deferred        libxdmcp.so.6
ELF f6e80000-f6eab000 Deferred        libxcb.so.1
ELF f6eab000-f6ff8000 Deferred        libx11.so.6
ELF f6ff8000-f700d000 Deferred        libxext.so.6
ELF f7051000-f70de000 Deferred        winex11<elf>
  \-PE f7060000-f70de000 \               winex11
ELF f70de000-f7237000 Deferred        user32<elf>
  \-PE f70f0000-f7237000 \               user32
ELF f7237000-f7365000 Deferred        gdi32<elf>
  \-PE f7240000-f7365000 \               gdi32
ELF f7367000-f736c000 Deferred        libdl.so.2
ELF f736e000-f7372000 Deferred        libxau.so.6
ELF f7372000-f7396000 Deferred        imm32<elf>
  \-PE f7380000-f7396000 \               imm32
ELF f7396000-f73b0000 Deferred        version<elf>
  \-PE f73a0000-f73b0000 \               version
ELF f73b0000-f7571000 Dwarf           libc.so.6
ELF f7571000-f758f000 Deferred        libpthread.so.0
ELF f758f000-f775d000 Dwarf           libwine.so.1
ELF f775f000-f7784000 Deferred        ld-linux.so.2
ELF f7786000-f7787000 Deferred        [vdso].so
Threads:
process  tid      prio (all id:s are in hex)
00000008 Bloodlines SDK.exe
["C:\Program Files\Steam\steamapps\common\Vampire The Masquerade - Bloodlines\Patch_Extras\Developer Tools\Bloodlines SDK\Bloodlines SDK.exe"]
00000009    0
0000000e services.exe
[C:\windows\system32\services.exe]
0000002b    0
00000026    0
00000020    0
0000001d    0
00000012    0
0000000f    0
00000010 explorer.exe
[C:\windows\system32\explorer.exe /desktop]
00000033    0
00000032    0
00000031    0
00000011    0
0000001a winedevice.exe
[C:\windows\system32\winedevice.exe]
00000025    0
0000001f    0
0000001e    0
0000001b    0
00000023 plugplay.exe
[C:\windows\system32\plugplay.exe]
00000028    0
00000027    0
00000024    0
00000029 winedevice.exe
[C:\windows\system32\winedevice.exe]
00000030    0
0000002d    0
0000002c    0
0000002a    0
00000034 cmd.exe
[C:\windows\system32\cmd.exe /c SDKBinaries\start_sdk.bat -int ]
00000035    0
00000036 (D) C:\windows\system32\wineconsole.exe
[wineconsole --use-event=12]
00000037    0 <==
0000003a explorer.exe
[C:\windows\system32\explorer.exe /desktop]
0000003e    0
0000003d    0
0000003c    0
0000003b    0
System information:
    Wine build: wine-2.9 (Staging)
    Platform: i386
    Version: Windows XP
    Host system: Linux
    Host version: 4.4.71-1-MANJARO
10
Bloodlines Modding / Re: Bloodlines SDK
« Last post by Psycho-A on June 20, 2017, 12:16:53 AM »
If you need any extra info from me, just let me know.
Yes, I will. First, please tell me: on what exactly stage of pre-installation or launching that error appears? I mean, what steps you already did before it appear (f.e. clicking on some notify messages, selecting mod destination folder etc.). Second, try to launch freshly-extracted SDK with the file "SDKBinaries\Start_SDK.bat" instead of native exe. It keeps the command prompt window opened, and when your issue will appear, you do the screenshot with the console window log and Wine error message over it. With this you will do a good help for me.
Pages: [1] 2 3 ... 10