sv6 struct? about openrct2 HOT 10 CLOSED

I expect most of the flags in the ride data will be the same. The ride structure is the same size as in RCT1, so its possible that more space was needed and therefore the structure was reorganised a bit.

Feel free to start adding this documentation to the wiki. I have copied all your findings so far into my IDA database. Several people now have the database, although all different versions. I am not sure the best way to merge them all and keep everyone up to date.

from openrct2.

Would it make sense to store it in git? The file format is readable...

Another relate problem is IDA 5 doesn't work with Macs and the formats are
incompatible (I think)

On Wednesday, April 30, 2014, Ted John [email protected] wrote:

I expect most of the flags in the ride data will be the same. The ride
structure is the same size as in RCT1, so its possible that more space was
needed and therefore the structure was reorganised a bit.

Feel free to start adding this documentation to the wiki. I have copied
all your findings so far into my IDA database. Several people now have the
database, although all different versions. I am not sure the best way to
merge them all and keep everyone up to date.

—
Reply to this email directly or view it on GitHubhttps://github.com/IntelOrca/issues/28#issuecomment-41781298
.

Kevin Burke | Twilio
phone: 925.271.7005 | kev.inburke.com

from openrct2.

I've added what we know about SV6 format to the wiki: https://github.com/IntelOrca/OpenRCT2/wiki/SV6-Ride-Structure

from openrct2.

I agree with putting it in the repository, github starts warning at 50MB that files are big, and they block files larger than 100MB. So I think adding an 8 MB file should not be a problem. And it will be easier to see what info gets added over time.

from openrct2.

It can be put in the repository, but I don't think its capable of diffs or merging with files this large.

from openrct2.

You're right, github can handle files as big as 5MB for all normal actions, else it can only be used as a raw file (https://help.github.com/articles/what-are-the-limits-for-viewing-content-and-diffs-in-my-repository). I could write a small tool to split them in a smart way and join them again so we can keep diffs working.
But also having them as raw file would be nice, so we can at least diff them with an external diff utility like winmerge or beyond compare. Although I don't know how git manages space if diffs are not possible, maybe it will be a new file every time and not only the differences, so it will be filling up the space available really fast.

from openrct2.

I tried playing with committing the IDA file locally and git is not happy with it.
It is a binary file with some plain text on it, but mostly binary. Git considers it binary and can't diff. Also, git will always store the whole thing again for every single change we do, which will make the repository quickly impractical to work with.
Github suggests using Git Large File Storage (Git LFS), which they support. This would keep only a "link" to the large file in the main repository, and keep the content somewhere else. Git LFS abstracts that from you, supporting regular git commands to work the file, it's all seamless.
Having it available easy would be of great benefit to everyone. Still, it's a binary file, very hard to code review, so I assume only "trusted" developers would would be allowed to commit it.

from openrct2.

If you open it you can see that it is not really a binary file, it is just a lot of plain text and I guess git reads it as binary just because it is larger than 5MB. I think we actually had a discussion about this in another place and I tried to make a application to split them in a smart way, but I never got really far with that. My idea was to split them in files of about 2.5MB and then when somethings gets added in between you those files would grow till they exceed 5MB at which point they would be split in two files of 2.5MB again.

from openrct2.

We might be talking about different files, my "openrct2.idb" is binary, here's the first line of it:
IDA1 > Cà%�H Q� M€Q�ÝÌ»ª� �öðËÆÚS ¾‹ý, KˆÖ² à%�
Anyway, for storing large files I have used Git LFS before and it does exactly what it advertises. Considering github supports it, I don't see any reason for us to create our own custom solution.

from openrct2.

Ok, the file I got from IntelOrca last time was an IDC file (one year ago, have not been active here for some time) which is only plain text, so this is the one I would put under source control.

from openrct2.