windows: 64bit support

[nillerusr]

• Saverestore is broken
• Release build crashing
• Explosion particles not displaying ( only under cdb debugger )
• Protocol is broken
• Maybe something else

[LegendaryGuard]

Be careful! The name is wrong, it isn't i386, it's amd64. Btw, good luck! 👍

[nillerusr]

shit happens

[EnderZip]

try launching the game without debugger attached or -dev
that kinda fixed the particles on my side

[nillerusr]

@EnderZip

game without debugger attached

Lol that's works. Even with -dev

[EnderZip]

Yeah strange ain't it, btw is sound working?

[nillerusr]

@EnderZip yeap is working

[EnderZip]

Ah well good to hear, keep up the good work

[nillerusr]

Well, protocol is broken

[EnderZip]

So you can't load into a map yet?

[LegendaryGuard]

The maps can be loaded successfully, but there are stuff to fix when I used .\waf.bat configure -T release --64bits to obtain the release build:

• When the projectile from Rocket Propelled Grenade is shot, the projectile touches a wall or something and doesn't collide and explode as should. The projectile stays stuck in the wall/ground and moves very slowly depending where you're guiding.

• Also SMG grenades, Crossbow arrow gets stuck incorrectly in the wall and pheropods doesn't mark the collision, just stays.

• Story mode: In Entanglement chapter, Alyx, after seeing and talking her dad, in the door doesn't open it and doesn't move from her place.

• In the console, this message is spamming, it happens when the player is coming near/touching a wall or something does:

AllocTouchLink: failed to allocate touchlink_t.

In the debug build (.\waf.bat configure -T debug --64bits -8), appears an error after Assertion window (#131 (comment)) and the game doesn't load:

[nillerusr]

@LegendaryGuard that's strange. I don't have problems with touchlink_t

[nillerusr]

@LegendaryGuard Don't use saves from 32bit engine

[LegendaryGuard]

@LegendaryGuard Don't use saves from 32bit engine

Worked. All safe. 👍

In the debug build (.\waf.bat configure -T debug --64bits -8), appears an error after Assertion window (#131 (comment)) and the game doesn't load:

Still I can't use the debug build, I tried attaching the process with VS IDE, I can't obtain any debug info... I think we won't be able to debug. 🤔

Well, protocol is broken

If it's broken, that means no multiplayer games can be played. 🤔

[nillerusr]

@LegendaryGuard

no multiplayer games can be played

yep, i even can't connect to local server

[LegendaryGuard]

I've a noob dev question:
How I compile to get HL2 Deathmatch or CS: Source? I never tried to compile specifically for a game like these (also HL1, DoD, Portal, ...), the target is always HL2 (besides engine compiled stuff, I always get the same compiled stuff with this game directory: hl2/bin).

[nillerusr]

@LegendaryGuard
./waf.bat --help

[LegendaryGuard]

I see, thanks for your hint. It's using --build-games=any_from_game_dir(cstrike, hl2mp, portal, ...) parameter
e.g. I built HL2 Deathmatch and compiled successfully with that configured build:

.\waf.bat configure -T release --build-games=hl2mp --prefix=../win64build_source-engine_HL2MP -8

Is normal for the compiled launcher to appear with the same name and icon: hl2_launcher?

[maotouxie]

Server uses different class tables

[nillerusr]

@LegendaryGuard of course that's normal, lol.
Run using -game hl2mp command-line argument

[nillerusr]

@HappyDOGE bullshit, у меня развалился протокол

[nillerusr]

@LegendaryGuard Can you check cstrike on 64 bit?