Programmatically you could.
It's the game's global gravity, so no. Halo 1 never had object-specific gravity scaling.Quote:
Originally Posted by Hunter
Printable View
Programmatically you could.
It's the game's global gravity, so no. Halo 1 never had object-specific gravity scaling.Quote:
Originally Posted by Hunter
Good stuff man, looks like I might actually have to get off my ass and reinstall HCE to try this.
Was that in reply to the field-edit question?Quote:
Originally Posted by Kornman00
I'll assume so. That is awesome, and offers actual hornet physics to be realised if it's true.
Yeah it was. You'd need to have a programmer obviously.
So the entire OS is completely updated to 1.09, not just the addresses that are used from the get-go?
All addresses that have been updated. Not all have been tested as not all are used (ie, campaign level extensions). But all which are used by active systems have been tested.
Ugh, sapien isn't playing nicely with what we were going for. Sadly, sapien will not be able to make use of tags folders in different root directories, however tool and guerilla still will. Ex, if sapien is located at "C:\halo1\sapien.exe", but the tags folder is located at "C:\halo2ce\tags", it won't be able to access those tags.
Sapien will however allow you to use different tag folder names as long as they're in the same directory as sapien (ie, ""C:\halo1\"). So you can three different tag folders in your HEK folder: "tags", "tagsh2ce" and "tags_BLAM" and then have profiles for each of those in your settings. From there, you can make shortcuts to sapien which then specify which profile you want sapien to use via the command line.
Something is better than nothing as they say :\. At least tool and guerilla will still work with tag folders existing anywhere on your computer.
I fixed mah Sapien a long time ago. Just nop'd a whole function that caused the dual-core error. Not the right way of doings things but I lol'd.
I just lost one or two days off my schedule. I was working on getting the codebase synced with the source control yesterday. Found out that there was an update to my SC's client so I updated that. Windows also told me it had a couple updates too so I figured since I had to restart my computer I'd perform the next sync after I rebooted. Well I reboot and W7 fails to launch. I tried a couple different things but I didn't google the BSOD error. Instead I just Installed a new copy of W7 onto a different partition and started the configuration process all over again (decided to see what the BSOD was all about this morning). So I've lost at least a day with having to redo my computer :\
Just like cellophane and having to get a rope, it's always something :ugh:
Don't worry. Recently I had bad sector on Windows DLLs. Was fun to fix it with no Windows CD, no Recovery and no Ubuntu.