Remnantmods

Scenario Placement SLC Fixer.

As we know, cloning placement chunks in the scenario such as scenery or obstacles, the new chunks won't show up on the client xbox because of that unique value it has is shared with the other new cloned chunks.

This app will recalculate that special value for all Scenery, Machine, Control, and Crate placements.
(Other placement types that are not included must be done by hand with this tut.)

If you add more placement chunks, you must use the app once more.



Credits:

JacksonCougar: Coded it.

DemonicSandwich: Convinced him to do so.

neodos: Originally found the Unique ID and it's significance.

Update: The file database is unavailable for now. http://files.remnantmods.com/demonicsan ... 0Fixer.rar

In fact he already made it when i asked him but it wasn't working properly.

The "special value" is called Unique ID... and i found it, even posted a tutorial about it, onyx map isn't fixed for that, but w/e kthxbye

coo

Changing the unique # does not fix this neodos, thats the first thing i tried, Hopefully this app will do more then generate a # for that box.
Ill test this later and post my results.

Ogrish wrote:Changing the unique # does not fix this neodos, thats the first thing i tried, Hopefully this app will do more then generate a # for that box.
Ill test this later and post my results.

You still need to use Entity to "Fix System Link" to reference the new tags.

OKAKAZZZ

Me and Soc tested my map after fixing with entity, then using this tool, and....
No still no syslink.

No, use this tool then fix with Entity.

Doesn't matter which order you do it in because the two actions do something entirely different.

The "Fix System Link" in Entity adds chunks to the "Predicted Resources" reflexive, then references SLC-breaking tags in those new chunks. Namely the collision box [bloc] tags and the collision testing weapon and projectile.

This app changes 4 bytes (offset 40) within several Placements reflexives. Changing them to different numbers so that no chunk shares the same number.

The reason is shouldn't matter is because the Predicted Resources comes well after all the placement reflexives.

Just for reference, Jackson and I did an SLC test of Outpost 11. I used this tool and we tried playing it. We stayed in blue screen the entire time.

Then I "Fixed System Link" with Entity, sent him the map once more and tried playing it. And did so successfully.

Basically, don't have one guy fix their copy of the map with their Entity and the other guy do so with their copy and their app.
Instead have one guy Fix System Link, and then send that copy to everybody.

i fixed syslink with 1.3.9 then used the tool then made a patch, patched a clean map to test, then sent patch to Socrates, and tested.

Hate to bump this, but I really need it and, well, all of the links don't work.

its on acemods.org the ftp server in a file called tools