TFC works flawless aside from Sniper Rifle animation/sound

[BaronKrause]

Just tested TFC (the steam installed version) as a mod in Xash32 FWGS on Windows using the newest precompiled release version (not newest source) and surprisingly it worked! It crashes the normal Xash3d.

Everything seems to work fine aside from the sniper rifles fire. It has that unique functionality where it needs to be held down to charge and the gun lifts up and displays the red dot on the target. In Xash3d FWGS it behaves weird, the gun animation doesn't go up all the way, and its sound is wrong too, almost like a tranq dart sound, that or that's a minor sound that plays along with the normal one, and now thats all you hear in its absence (i remember hearing that sound along with the normal firing sounds of other weapons for instance). It doesn't leave a mark on the wall where you shot either.

It Does work though, testing with 2 simultaneously running clients in a LAN it still insta gibs on headshot so it not totally busted. Its just weird.

Everything else works perfect so i'm hoping it's some very minor tweak, if that's even something anyone wants to look at considering it is a mod (although an official one).

Its using the same steam version of half life as a base that it normally runs fine in. When running using the hl.exe instead of the xash_vc.exe in that same installed folder, the sniper rifle functions correctly, so it must be a quirk with the way Xash3d is handling that 1 weapon right?

[Edit]
Just tested, the result is the same when using the linux build of Xash3d/Half-Life/TFC

[nekonomicon]

Xash3D FWGS 0.19.x based on Xash3D 0.98(build 3366) that has a big bunch of bugs with client weapon prediction.
It's probably will be fixed in Xash3D FWGS 0.20 but need testing.

[a1batross]

And maybe even broken.

@BaronKrause you can try to run it under "new engine", it's source located in xash3d-fwgs repo. If you don't want to build it from source, automatically built engine is pushed to xash3d-deploy repo, branch "newengine-master".

[BaronKrause]

And maybe even broken.

@BaronKrause you can try to run it under "new engine", it's source located in xash3d-fwgs repo. If you don't want to build it from source, automatically built engine is pushed to xash3d-deploy repo, branch "newengine-master".

@a1batross Ill try that!
After downloading it on windows, do you know what Im supposed to do with the files? The instructions said to first download the normal release version, then replace the files with the testing ones.

After downloading the newengine-master branch, I have 4 files.

"Xash3DFWGS-i386.AppImage"
"xash3d-mingw.7z"
"xash3d-osx.tar.bz2"
"xash3d-vc.7z"
"xash3d-vc2008-sln.7z"

When extracted with 7-zip the i386.AppImage looks to be linux .so files, the osx version is im assuming files for the OSX version, and the vc file contains "SDL2.dll" and "vgui.dll"

"xash3d-mingw.7z" cant be opened as an archive in 7-zip and it doesn't look to be a direct replacement of any file. Is it just the "SDL2.dll" and "vgui.dll" files to copy over to test the new engine on windows?

[a1batross]

You're intended to run this AppImage file. Just make executable and it should work. Will look why vc build is failed, thanks. чт, 23 мая 2019 г., 4:59 ПП BaronKrause <notifications@github.com>:

…

And maybe even broken. @BaronKrause <https://github.com/BaronKrause> you can try to run it under "new engine", it's source located in xash3d-fwgs repo. If you don't want to build it from source, automatically built engine is pushed to xash3d-deploy repo, branch "newengine-master". @a1batross <https://github.com/a1batross> Ill try that! After downloading it on windows, do you know what Im supposed to do with the files? The instructions said to first download the normal release version, then replace the files with the testing ones. After downloading the newengine-master branch, I have 4 files. "Xash3DFWGS-i386.AppImage" "xash3d-mingw.7z" "xash3d-osx.tar.bz2" "xash3d-vc.7z" "xash3d-vc2008-sln.7z" When extracted with 7-zip the i386.AppImage looks to be linux .so files, the osx version is im assuming files for the OSX version, and the vc file contains "SDL2.dll" and "vgui.dll" "xash3d-mingw.7z" cant be opened as an archive in 7-zip and it doesn't look to be a direct replacement of any file. Is it just the "SDL2.dll" and "vgui.dll" files to copy over to test the new engine on windows? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#453?email_source=notifications&email_token=AAYQTAJJYV7BKDMERLBUWTLPW2PKJA5CNFSM4HOWYAOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWCJ43Y#issuecomment-495230575>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAYQTALVYJUSVSOGPB2NJKLPW2PKJANCNFSM4HOWYAOA> .

[BaronKrause]

@a1batross just tried the travis version instead that had a xash3d-mingw.7z that was extractable (your right, the first one must of failed since it is 1KB) and copied it over and ran the new xash_sdl.exe. That worked but it still has the same TFC sniper rifle quirk.

Unsure if the Travis version is much different than the standard new engine branch though.

[a1batross]

Ehhh... you shouldn't copy new engine binaries over the old ones anymore.

And yeah, "travis" branch prefix only for old engine. New Engine is being pushed to "newengine" branches.

[mittorn]

New engine does not support windows at this moment
@a1batross, Please check travis, it does not report errors if deploy stage completed successfully