Zeblote

It doesn't, but it isn't an issue, as PhysX 5 is not being licensed for games anyway.

Adding support for VS 2022 yourself is quite easy. I have done so here. https://github.com/Zeblote/PhysX/commit/00180480a25c8ac6172d3703a4939af8dc06812b

Worth noting that my branch is specialized for brickadia, it might not be ideal for all uses cases, for example shared shapes are broken.

I really don't understand it. What is supposed to be the point of it being exclusive to Omniverse? Being able to set up my simulation in Omniverse is entirely useless...

You can't! Amazing, right?

> there is typo on the linked page :( The page has many errors, such as calling it an SDK, when none exists.

There are only two things I need from PhysX 5: - the custom collision callback thing. - all of the misc optimizations that were made since PhysX 4.1. All this...

The most infuriating thing about this is the complete lack of communication. First you say PhysX 5 is just around the corner - two years ago. Then you say an...


``` [0x6d5c|00:00:04.072] Patch progress: 12 % [0x6d5c|00:00:04.079] Patch progress: 13 % [0x6d5c|00:00:04.085] [hpatch] check _file_append_part(self,writeToPos,data,data+writeLen) error! [0x6d5c|00:00:04.087] [hpatch] check patch_decompress_with_cache(out_newData,oldData,&hdiffData.base, self->_decompressPlugin,temp_cache,temp_cache_end) error! [0x6d5c|00:00:04.087] [hpatch] dir patch run ERROR! [0x6d5c|00:00:04.087] [hpatch]...