Recent Posts

Pages: [1] 2 3 ... 10
1
PATCHES / Re: Wesp should be banned from Steam for lieing
« Last post by Tessera on December 10, 2017, 10:09:17 PM »
I'm going to keep it in here since it's steam related, but can someone tell me what Wesp is on about here?

From a steam discussion:

"You should be aware that the True Patch adds needless changes to the gameplay nowadays, just check out the room of the sisters in the Asylum and compare it with the original game. There might be more changes like that so don't believe that this patch does nothing but bug fixes..."

I'm honestly not certain what he's referring to.

He's referring to the one and only modification that I added to the Asylum club map. Instead of just standing in one place like statues, up in their office, I allowed both Therese and Jeanette to roam around a bit within the office. Nothing much really, just allowed them to do things like answer a cell phone call, or use their laptop computer, or lean up against the wall... that sort of thing.

I agree that it's a mod... so hey, I'm guilty as charged. But I always hated the way NPC's just stand rooted in one place in RPG's. It's not very natural, so I allowed the Voerman sisters to move around a little bit.

Incidentally, this is one of only two arbitrary changes that were introduced within the True Patch series. The other is the extended "ghouling Heather" scene that also occurs in Santa Monica, during the early game. Both were added with the intent of slightly enhancing the realism of each scene. Nothing major was changed in either case. The scene with Heather was actually mostly written by Troika, but the Malk-specific dialogue was unfinished, so they cut it from the final release of the game. All we did was write some new dialogue for the Malks and then add that scene back into VTMB.

The last thing I'll say is this: if Wesp is really trying to keep score here, then it works out like this...

(1) Number of arbitrary changes added by the True Patch: 2.
(2) Number of arbitrary changes added by Wesp's "patch:" about 70 or so ridiculous and unnecessary changes, many of which undermine the gameplay and the mood of VTMB. (Schu counted them all a few years back... and by now, it must be double what it was back then.)
(3) Number of new bugs added by the True Patch: absolutely none.
(4) Number of new bugs added by Wesp's "patch:" dozens and dozens. No really... it's quite a large number and we've lost count over the years. Wesp has broken more things than he's fixed in VTMB.
(5) Which patch fixes more LEGITIMATE bugs: the True Patch, hands-down. Most of Wesp's so-called "repairs" are repairs to items that he himself broke in one of his previous releases.

So okay... neither of us is 100% innocent, but the TPG wins on its overall score alone. We've fixed more bugs than Wesp, we've NEVER broken anything at all, and aside from those two small arbitrary additions to the Santa Monica chapter of the game, we've left everything else exactly the way that Troika intended it to be. :P
2
PATCHES / Re: Wesp should be banned from Steam for lieing
« Last post by Prisoner416 on December 10, 2017, 06:37:56 PM »
I'm going to keep it in here since it's steam related, but can someone tell me what Wesp is on about here?

From a steam discussion:

"You should be aware that the True Patch adds needless changes to the gameplay nowadays, just check out the room of the sisters in the Asylum and compare it with the original game. There might be more changes like that so don't believe that this patch does nothing but bug fixes..."

I'm honestly not certain what he's referring to.
3
PATCHES / Re: True Patch Gold Edition -- DIRECT DOWNLOAD LINK
« Last post by Prisoner416 on December 09, 2017, 12:13:57 PM »
Nice to see that work is still being done, amazed with the graphics dx progress.

Well, I have some bad news. I have decided NOT to release the DX9 graphics upgrade, mainly because it would go against the tradition of the True Patch series. It isn't a bug fix... it's a mod and with only a few small exceptions, I've always tried to avoid adding any mods into the True Patch.

I may release it separately as a VTMB graphics mod --  we'll see. It isn't actually mine, anyway... all I've done is take the SweetFX mod and re-tune it for VTMB. And while it's true that I also made a couple of code changes to the VTMB engine, in order to make it work better with SweetFX, it's still a mod -- not a bug fix. SO... I won't be including it within the True Patch. Sorry, folks. :'(

It seems that the solution should be simple if he can address it with his. It seems like there's a fix with the vampire.dll file that bypasses the problem.

Yes... it's a line of code that tells the engine to search for the SafeDisk driver, prior to loading the main menu. But as I have said, I have no interest in supporting Windows 10 -- therefore, I won't be bothering with it. If someone in the VTMB community wants to submit their own "TPG on Windows 10" fix for this issue, then by all means... go ahead and do so, with my blessing. 

Truth be told, folks... for the past 11 years, I've done my bit to support VTMB. More than my bit, frankly. The TPG is still the best patch on the web for VTMB, and it doesn't need any further enhancements.

Of course, the rest of you are free to make your own alternative patches -- if you feel that the TPG is somehow flawed or inadequate.

Way back on December 14, 2011, I stumbled into this forum having found out about the patch, asking some stupid questions in retrospect about the two patches. I thank you, deeply, for doing this much for this long.

I hope someone does or you consider your own release. At the moment I'm running the true patch but with the dll file from the other thing.

Seems to work so far... only error I noticed was that after the intro execution, it showed a blank hall instead of the characters leaving. I think that happened to me before in pure runs anyway though. Also the beheading scene is missing.

Honestly, I'd do the work myself if I could just to make sure the file was untainted by wesp. I can only pray that someone with better knowledge takes a stab.

I'd love to work on the scripts for the game, fix the subtitles to match the spoken dialog in most cases (There are a lot of cases where the subtitles are lacking), and do the basic grammar tweaks. Not sure if it'd be worth starting it up as a project though if development for the patch is done.


4
PATCHES / Re: True Patch Gold Edition -- DIRECT DOWNLOAD LINK
« Last post by Tessera on December 09, 2017, 09:47:53 AM »
Nice to see that work is still being done, amazed with the graphics dx progress.

Well, I have some bad news. I have decided NOT to release the DX9 graphics upgrade, mainly because it would go against the tradition of the True Patch series. It isn't a bug fix... it's a mod and with only a few small exceptions, I've always tried to avoid adding any mods into the True Patch.

I may release it separately as a VTMB graphics mod --  we'll see. It isn't actually mine, anyway... all I've done is take the SweetFX mod and re-tune it for VTMB. And while it's true that I also made a couple of code changes to the VTMB engine, in order to make it work better with SweetFX, it's still a mod -- not a bug fix. SO... I won't be including it within the True Patch. Sorry, folks. :'(

It seems that the solution should be simple if he can address it with his. It seems like there's a fix with the vampire.dll file that bypasses the problem.

Yes... it's a line of code that tells the engine to search for the SafeDisk driver, prior to loading the main menu. But as I have said, I have no interest in supporting Windows 10 -- therefore, I won't be bothering with it. If someone in the VTMB community wants to submit their own "TPG on Windows 10" fix for this issue, then by all means... go ahead and do so, with my blessing. 

Truth be told, folks... for the past 11 years, I've done my bit to support VTMB. More than my bit, frankly. The TPG is still the best patch on the web for VTMB, and it doesn't need any further enhancements.

Of course, the rest of you are free to make your own alternative patches -- if you feel that the TPG is somehow flawed or inadequate.
5
PATCHES / Re: True Patch Gold Edition -- DIRECT DOWNLOAD LINK
« Last post by Prisoner416 on December 08, 2017, 10:22:36 PM »
Nice to see that work is still being done, amazed with the graphics dx progress.

However, I do hope you consider making a patched .exe file for those of us that were forced into using Windows 10, since there is the crash on new game.

I HATE the fact that Wesp's "Patch" fixes the issue. I'd rather not corrupt my game with it, even if it allows it to run.

It seems that the solution should be simple if he can address it with his. It seems like there's a fix with the vampire.dll file that bypasses the problem.

Sadly, more and more people will have Windows 10 soon, and Windows 7 is no longer available for purchase. I'd hate to see many people, including myself, miss out on the best patch for the game just because of that simple compatibility issue. I know you've made your stance clear, but I do hope you'll consider looking into it someday, if only to preserve this historic game.


6
PATCHES / Re: Windows 7 Update and Windows 10 issue
« Last post by Tessera on December 07, 2017, 05:11:11 PM »
sorry, my SSD is 1 TB, had an existing windows install on it already.
The issues arose when I unplugged one of my standard HDD's to install the new standard 10TB HDD.
All shit is fine in BIOS, all drives detected. There is no longer a problem since I was forced to (once again) re-install windows.

Yuck... well, glad you finally got it straightened out.
7
PATCHES / Re: Windows 7 Update and Windows 10 issue
« Last post by krakr on December 07, 2017, 12:39:19 PM »
sorry, my SSD is 1 TB, had an existing windows install on it already.
The issues arose when I unplugged one of my standard HDD's to install the new standard 10TB HDD.
All shit is fine in BIOS, all drives detected. There is no longer a problem since I was forced to (once again) re-install windows.
8
PATCHES / Re: Windows 7 Update and Windows 10 issue
« Last post by Tessera on December 07, 2017, 08:31:11 AM »
Win7x64 doesn't like SSD's , so it creates a BOOT dir on the next available HDD. Unplugging that creates issues, apparently f'd up issues that require reinstallation of the OS. Too drained mentally to go into more detail now, but there you have it.

Not exactly. I'm using Win 7 x64 with a Samsung SSD and everything works fine. Samsung SSD's are bundled with special software which clones your existing drive to the SSD, sets up the correct Windows boot sectors and partitions, and so forth. Then you just switch over to the cloned SSD and all is well.

In your case, I think a good part of the problem is due to the enormous SIZE of your SSD. You did say 10 TB, yes..? Also, your system BIOS may not be configured properly for a large SSD.

There was no such thing as a 10TB drive back when the Windows 7 kernel was developed... and while it should be possible for Win7 to read and write to a drive that size (after the proper drivers have been installed), it may not be able to actually BOOT from a drive as huge as 10TB. Keep in mind that until Windows finishes loading all of its AHCI drivers and so forth, it won't even recognize a drive of that size. Natively, the Windows 7 kernel doesn't recognize anything much larger than 512 GB.

By the way... did you go into the system BIOS and change your HD controller to AHCI mode, after installing the new SSD..? Because most SSD's... especially very large ones... won't work properly unless they run from an AHCI-enabled controller.

Also, Windows 7 always installs a 100 MB EFI system partition on whatever drive the OS is installed to. If that drive is larger than a certain size, then it looks for a different drive to install its EFI partition to. So once again, in your case, your SSD is simply too large for the Win 7 OS to boot from.

A workaround might be to create primary partitions on the drive, prior to placing any data on it. The first partition, which I presume will be for your Win7 OS, should be no larger than 512 gigabytes. Windows doesn't need a boot partition any larger than that -- I personally use a 256 GB boot partition in my rigs. Create the partitions, then quick format them, and the new SSD should be ready to go.

Samsung SSD's come bundled with excellent software (Samsung Magician; Samsung Data Migration Wizard) that make the process of moving your existing OS over to a new SSD almost painless. I don't know if other brands of SSD's come with similar software... I would hope so.

Like I said -- until Windows finishes loading all of its motherboard AHCI drivers, it doesn't even know what to do with a 10TB drive. You're trying to force Windows 7 to load from a drive that is 20 times larger than anything that was available back when Windows 7 was being developed. The system drivers that came with your motherboard will allow Windows to "see" those enormous drives, but those drivers don't even kick in until after Windows 7 has finished booting up.

So here's my advice:

(1) Make sure your hard disk controller is set to AHCI operation in your system BIOS. Most large SSD's depend upon this.
(2) Create a 256 - 512 gigabyte primary partition on the SSD, prior to installing any data on it.
(3) Install (or clone, if your SSD came with the appropriate software) Windows 7 x64 to that partition.
(4) Hook everything up and the system should boot from the SSD. If not, then you might consider getting a smaller (~256 GB) SSD and using it for just the Windows boot drive, and your larger SSD can be used for everything else.
(5) All computers... regardless of what they are or how they are set up... will run more smoothly and efficiently if you partition very large hard drives into multiple, smaller partitions (as opposed to a single enormous partition). There are several reasons for why this is true -- feel free to research it, if you are curious.
9
PATCHES / Re: Windows 7 Update and Windows 10 issue
« Last post by krakr on December 06, 2017, 09:17:25 PM »
Well, this is fun.
Just bought a 10 TB HDD for my rig, installed it and Windoze refused to boot. Even after I restored it to it's old configuration (without the new HDD since my MOBO supports 6 SATA devices and I had 6 counting my dvd/rw) . Seems MS & SSD's don't like each other. (my boot drive is the SSD) So I sent them a nastygram asking if they were spreading ransomware:

https://answers.microsoft.com/en-us/windows/forum/windows_7-update/is-there-a-new-ransomware-in-one-of-the-windows-7/e3d6d71c-f38a-4ddd-9194-03a594f0fe47?messageId=fddf44ac-35bf-4b94-ba50-421ce1136c4f

Read the response for yourself if you like. Thankfully, I posted on a few forums and got a knowledgeable response. Didn't actually help me since I had to re-install anyway, but it gave me an answer. Win7x64 doesn't like SSD's , so it creates a BOOT dir on the next available HDD. Unplugging that creates issues, apparently f'd up issues that require reinstallation of the OS. Too drained mentally to go into more detail now, but there you have it.

Oh, & sorry for the direct link to M$, I can't remeber the anonymizer pre-link off the top of my head. If it's a major issue I would take it as a kindness for a Mod to edit the link, otherwise I will do it myself in the next 2 days or so (I have 138 windows updates pending)
Just thanking Satan I have a reference to the KB# here so I can uninstall it again. Wish I knew what KB fucked my system this time.
10
PATCHES / GoG and the True Patch
« Last post by Tessera on November 12, 2017, 09:21:10 PM »
Some Answers Regarding The GoG Version of Bloodlines

About a dozen or so people have sent me e-mails regarding the Good Old Games version of VTMB, which happens to be "pre-patched" with Wesp5's awful "unofficial patch." Specifically, people have asked me (1) is it possible to remove Wesp's crap from the GoG version of the game and (2) can the True Patch then be installed and (3) will the True Patch be compatible with modern hardware and operating systems. So let me address those questions one at a time:


(1) Is It Possible to Remove Wesp's Crap From The GoG Version of Bloodlines..?

Yes and no. The staff over at GoG have released a script which supposedly removes most of Wesp's nonsense from their version of VTMB. But I took a quick look at it... and it seems that some remnants of Wesp's junk will still remain, even after running the GoG clean-up script. More about their script can be found here, on the GoG web site...

https://www.gog.com/forum/vampire_the_masquerade_series/vote_for_a_vanilla_v12_build_of_vtm_bloodlines/page1

I will mention in passing that I noticed the not-so-suprising appearance of Wesp within that thread and sure enough, he continues to spew the exact same lies and disinformation about the True Patch that he has been babbling for the past decade. Needless to say, everything that Wesp has said within that thread is absolutely and totally false, and deliberately misleading on his part. One would think that Herr Wesp would have outgrown that childish bullshit by now -- but apparently, he hasn't.  ::)


(2) Can the True Patch be Installed, After Cleaning up the GoG Version Using Their Script..?

I honestly don't know. The fact that the GoG script DOES NOT totally remove all of Wesp's crap leads me to think that there might be some problems with installing the TPG into the GoG version of VTMB. I have no interest in testing it personally, so I'll have to rely upon the community to test it out and see whether or not it works properly. The TPG was developed and intended for use with either the original 3-CD boxed version of Bloodlines, or else the downloadable Steam release of the game. No other versions of VTMB are supported... because frankly, all of the other versions of VTMB are illegitimate in my view.


(3) Is The TPG Compatible With Modern Hardware and Operating Systems..?

The True Patch Gold Edition will work perfectly well on all modern hardware. Our patch contains code which enables the VTMB engine to recognize large amounts of system memory, modern video cards, and so forth. I personally run VTMB on the Windows 7 Ultimate x64 operating system. My computer has a modern Intel Core i7-6700K "Skylake" CPU and 32 GB of system RAM. My video card is a fairly new AMD Radeon R9 390 model, with 8 GB of on-board VRAM. VTMB runs perfectly on my setup, and it needs nothing more than the True Patch Gold Edition installed. So the answer to the question of whether or not the TPG is compatible with modern hardware is a resounding YES.

The bigger issue is the operating system. Windows 10 does not contain the support files needed to run VTMB... and about a thousand other PC games from that era. On Windows 7, VMTB runs just fine with the True Patch -- after you have re-enabled the SafeDisk driver that MicroSoft quietly disabled with a Windows update a few years ago.

But on Windows 10, it probably won't run at all. Windows 10 completely lacks the SafeDisk/SecureROM driver that the VTMB engine expects to find. Even if you use a hacked "NO-CD" executable, the game engine itself still runs a quick check for the presence of that driver and, if it fails to find it, the game will abort. This was never an issue until Windows 10, hence I have never done anything to fix it. And since I have absolutely no intention of ever buying and installing Windows 10 on any of my own computers, I doubt that I will -ever- attempt to fix this issue.

The TPG contains "no-cd" code that allows you to play the game without having to insert any CD's, but it does NOT bypass the start-up check for the presence of the SafeDisk/SecureROM driver (secdrv.sys). Hence the driver needs to be present and functional within your Windows operating system, even though the TPG version of the game will not actually use it. Weird, I know... but as I said, this was never an issue until the release of Windows 10. So like... go yell at Microsoft. Or just use Windows 7... it's a better OS for gaming, anyway.

BOTTOM LINE: The True Patch Gold Edition is fully compatible with modern computer hardware, and is likewise compatible with all versions of Windows -except- Windows 10. As for whether or not the TPG can be installed into the GoG version of Bloodlines, that remains to be seen. Community testing is needed, before the GoG issue can be resolved.

MY PERSONAL RECOMMENDATION: Do not purchase VTMB from Good Old Games, until they have fully resolved this issue. Buy it from Steam instead. No one should be selling a "pre-patched" version of Bloodlines... and yes, I would say the same thing even if it was the TPG that they were "pre-patching" it with. The plain-vanilla version of Bloodlines is the ONLY version that ANYONE should be selling, PERIOD. If you actually want a pre-patched version of the game for some weird reason, then just go download it via The Pirate Bay for free. But don't give your money to people who are trying to profit from community-made content. In my considered opinion, GoG are behaving like opportunistic leeches in this matter... so if you agree, then simply do not support them by purchasing any of their games.



Pages: [1] 2 3 ... 10