Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POTS physics flags are not always preserved #10

Open
diafero opened this issue Mar 15, 2012 · 3 comments
Open

POTS physics flags are not always preserved #10

diafero opened this issue Mar 15, 2012 · 3 comments

Comments

@diafero
Copy link
Member

diafero commented Mar 15, 2012

The physics flags from POTS are not always properly preserved, which makes edit POTS age files with PrpShop a problem: You will loose information, even if you change an object totally unrelated to physicals.

Some examples:
Reading TPOTS/dat/Myst_District_Fireplace.prp...
<28|1>[003F]d_sw colGroup changed: 0x00000000 => 0x00020000
<28|1>[003F]FireplaceDoorExclRegMesh colGroup changed: 0x01020000 => 0x01000000
<28|1>[003F]fireplaceExcludeRegionMesh repGroup changed: 0x00020000 => 0x00000000

Reading TPOTS/dat/Kadish_District_opt-kdshCourtyardPhysLeaves.prp...
<22|19>[003F]RedLeaf00b colGroup changed: 0x03800000 => 0x03000000
<22|19>[003F]RedLeaf01b colGroup changed: 0x03800000 => 0x03000000
<22|19>[003F]RedLeaf02b colGroup changed: 0x03800000 => 0x03000000
<22|19>[003F]RedLeaf03 colGroup changed: 0x03800000 => 0x03000000
<22|19>[003F]RedLeaf04 colGroup changed: 0x03800000 => 0x03000000

Reading TPOTS/dat/GreatZero_District_LinkInRoom.prp...
<39|3>[003F]OuterSphere colGroup changed: 0x00000000 => 0x00020000

@branan
Copy link
Member

branan commented Nov 28, 2012

@Hoikas is this issue totally resolved by #13? Can we close this?

@Hoikas
Copy link
Member

Hoikas commented Nov 28, 2012

I'm pretty sure @diafero has 99.99% fixed this--but I'd like his input before we close this issue for sure.

@diafero
Copy link
Member Author

diafero commented Nov 28, 2012

I improved the situation, but did not fix it: There are still a bunch of
objects in original Uru:CC which are not written back the way they are read.

So no, this is not fixed.

diafero

On 28/11/12 02:16, Adam Johnson wrote:

I'm pretty sure @diafero has 99.99% fixed this--but I'd like his input before we close this issue for sure.


Reply to this email directly or view it on GitHub:
#10 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants