Studio Connectivity Data


Studio Connectivity Data
#1
How is Studio's connectivity data stored? Is it documented in any way or in format that is/can be made readable?
Reply
RE: Studio Connectivity Data
#2
(2022-07-03, 21:41)Orion Pobursky Wrote: How is Studio's connectivity data stored? Is it documented in any way or in format that is/can be made readable?

It’s stored in .conn files that basically shadow the main part file. They’re quite readable.
Reply
RE: Studio Connectivity Data
#3
(2022-07-03, 23:29)N. W. Perry Wrote: It’s stored in .conn files that basically shadow the main part file. They’re quite readable.

 I wouldn't really call those readable, the way data is stored in those is very confusing, and there's no documentation on it
Reply
RE: Studio Connectivity Data
#4
(2022-07-03, 23:59)Max Murtazin Wrote:  I wouldn't really call those readable, the way data is stored in those is very confusing, and there's no documentation on it

They’re text files, aren’t they? I’m sure I have read them before.
Reply
RE: Studio Connectivity Data
#5
(2022-07-04, 3:05)N. W. Perry Wrote: They’re text files, aren’t they? I’m sure I have read them before.

I found them. It's a binary format which is a bummer.

Edit: Part designer has text based files though but license inside them
Reply
RE: Studio Connectivity Data
#6
(2022-07-04, 3:08)Orion Pobursky Wrote: I found them. It's a binary format which is a bummer.

Edit: Part designer has text based files though but license inside them

What files you mean?
Reply
RE: Studio Connectivity Data
#7
(2022-07-04, 11:24)Max Murtazin Wrote: What files you mean?

The collision files (.col) are text files. Pretty obscure nonetheless 😔
Reply
RE: Studio Connectivity Data
#8
(2022-07-04, 13:53)Philippe Hurbain Wrote: The collision files (.col) are text files. Pretty obscure nonetheless 😔

Collision files are just that, collision files. There's really nothing actually useful about those since they are only used for collision check, and the way Part Designer generates those is usually pretty bad
Also they are at least more or less readable, I guess it is some strange way of describing collision boxes. Probably 5 numbers for it is just enough
Reply
RE: Studio Connectivity Data
#9
(2022-07-04, 13:53)Philippe Hurbain Wrote: The collision files (.col) are text files. Pretty obscure nonetheless 😔

Why do they even need collision files? Testing mesh collision is a basic 3D task.
Reply
RE: Studio Connectivity Data
#10
(2022-07-04, 15:02)Orion Pobursky Wrote: Why do they even need collision files? Testing mesh collision is a basic 3D task.

Studio is a very riddling piece of software, and lacks some basic optimization in many places, so I guess they simply have some problems with that easy of a thing
Reply
RE: Studio Connectivity Data
#11
(2022-07-04, 15:02)Orion Pobursky Wrote: Why do they even need collision files? Testing mesh collision is a basic 3D task.
But many LDraw parts have no clear interior, eg. the studs lying on top of bricks... Maybe this requires more processing?
Reply
RE: Studio Connectivity Data
#12
(2022-07-04, 3:08)Orion Pobursky Wrote: I found them. It's a binary format which is a bummer.

Edit: Part designer has text based files though but license inside them

Maybe it's that I've edited them in Part Designer? I just know I've worked directly with the .conn files somehow. Perhaps nothing more that copy/pasting them to give connectivity to a patterned part, e.g.?
Reply
RE: Studio Connectivity Data
#13
(2022-07-05, 1:37)N. W. Perry Wrote: Maybe it's that I've edited them in Part Designer? I just know I've worked directly with the .conn files somehow. Perhaps nothing more that copy/pasting them to give connectivity to a patterned part, e.g.?

PartDesigner finally decided to behave and open on my machine. If you create a part and save it, it's in text format. The relevant meta seems to be PE_CONN but there's no documentation on how to use it.
Reply
RE: Studio Connectivity Data
#14
(2022-07-05, 1:51)Orion Pobursky Wrote: PartDesigner finally decided to behave and open on my machine. If you create a part and save it, it's in text format. The relevant meta seems to be PE_CONN but there's no documentation on how to use it.

There's no documentation for much of anything in Studio. And we can't help write it because the format isn't open…
Reply
RE: Studio Connectivity Data
#15
(2022-07-05, 1:51)Orion Pobursky Wrote: PartDesigner finally decided to behave and open on my machine. If you create a part and save it, it's in text format. The relevant meta seems to be PE_CONN but there's no documentation on how to use it.

I wouldn't say so. For Studio to load connectivity it only needs to have .conn file matching in name
Reply
RE: Studio Connectivity Data
#16
Presumably, if we can figure out the Meta commands, we can have something that can convert between LDCad and Studio metas. From there it would just be a matter of loading the part into PartDesigner and adding it to Studio. Even better would be to figure out the binary format and direct convert but that's a lot harder.

Maybe we can coerce the Studio team to document their custom Metas but I'm not holding my breath.
Reply
RE: Studio Connectivity Data
#17
(2022-07-05, 13:44)Orion Pobursky Wrote: Presumably, if we can figure out the Meta commands, we can have something that can convert between LDCad and Studio metas. From there it would just be a matter of loading the part into PartDesigner and adding it to Studio. Even better would be to figure out the binary format and direct convert but that's a lot harder.

Maybe we can coerce the Studio team to document their custom Metas but I'm not holding my breath.

Are there many meta commands tho? I can only remember two, and only useful is the texture one. By the way, apparently Studio texture command can also do projection mapping, not only UV
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 1 Guest(s)