Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Cheddarius]

Yeah, you don't actually always see people incrementing in .1 or .01 every time. Actually, I think I've almost never seen something that had a perfect version thing like that, +.1 every single time... and +.01 every time is just ridiculous, you'd have to have at least a hundred increments. Much better just to package many improvements in a larger package.

[Hippoman]

Well i've never released anything so I wouldn't know. Thanks for telling me.

[Cheddarius]

I haven't either, but look at, for example, the versions for Mozilla Firefox, or really, any software you download with versions. It's 2, then 3, then 3.5, then 3.6. And 3.0 just went up to 3.0.19, then it leaped... four hundred versions or so to 3.5.

[carebear]

It's all about what has changed. V1.0 would be a full release. Calling the next 1.001 would be appropriate for a small fix/addition. Maybe 1.01 for several fixes/additions. 1.1 has some significant changes. 2.0 is a large overhaul over the 1.x versions.

But for incomplete releases I wouldn't know. But it doesn't really matter. Going from 0.2x to 0.3 sounds logical for something such as having a new Dwarf Fortress release in your package.


Anyway this pack is looking good. Now that RantingRodent is taking a long break I'm rooting for this one! 

[Ironhand]

Thanks guys!

Bad news, unfortunately: I probably won't be getting 0.30 out this weekend.
I'm kinda getting behind in a (real) project. So I'm gonna focus on that this weekend.

Sorry.

Look forward to something next week, though.

[Martin]

Yes, from .23 all the way to .30 is .07 versions skipped correct?

Version numbers aren't usually linear that way. Typically each digit, or maybe each pair, constitute a series of revisions within a larger revision block. So for instance with the DF numbers:

0.31.06

The 0 refers to the major version. This is alpha, so Toady is still working toward the first version.

31 refers to the major features (arcs, bloats, whatever system he's worked out). Going from 2D to 3D was an increase of one in this count. Between releases, there might be 3 or 4 major additions, so it might jump from .31 to .35. To Toady, this is a linear increase as he's got .32 and .33 and .34 versions, but they weren't released.

06 refers to the minor features. This is like the one above, but these usually increment approximately with each successful build. Again, not every one may get released so it could jump to .08 if .07 was problematic.

Each developer has their own way of doing this. Knuth is using pi for his versioning for TeX so his current version number is 3.1415926. The next release would be 3.14159265. Each release adds a digit. Version numbers aren't even slightly user-friendly - they're entirely for the benefit of the developer.

[BlackRogue]

that's pretty much my understanding of how versioning numbers works

[Hippoman]

You learn something new in each random thread.

[gtmattz]

I came in here looking for more info on this fairly awesome graphics set, and end up reading a page worth of discussion on version numbering....

Derail much?

NOW FOR THE ON TOPIC PART!

SUPER AWESOME GRAPHICS SET MR. IRONHAND, KEEP UP THE GOOD WORK, I AM LOOKING FORWARD TO SEEING THE FINISHED PRODUCT!
 

[Aklyon]

I came in here looking for more info on this fairly awesome graphics set, and end up reading a page worth of discussion on version numbering....

Derail much?

Not really. It was related to the versioning of the graphics set, which is still talking about the graphics set in someway.

[Ironhand]

It really was kinda unnecessary.
We got the same explanation like three times in a row.

But whatever. Back on topic and all that. Thanks, gtmattz!

[Deon]

We got the same explanation like three times in a row.

People like the repetition. They think if they say something after another man, it will sound more menacing or real.

And I look forward for 0.3 . Oh wait, 0.30. Or will it be 0.301?

[HLBeta]

I'm trying to get this working on my Mac and have run into a bizarre difficulty. I can get the tileset working just fine in windowed mode but as soon as I switch to fullscreen the color values go all wonky. Most of my creatures are now blue, the beds are green and any bluish color seems to shift into the red-orange range. I have no idea as to what could causing this so I must appeal to your greater knowledge of the init files.

I would also appreciate it if some manner of installation guide was made available, I have yet to find one that works with the v0.31 releases.

[Ironhand]

That is weird!

You shouldn't have to install anything... it's all packaged together already.
It's probably easier to just move your save into my version of the game.
Make sure to update the raw files within your save folder too, though.

As for the Mac thing, I really have no idea... for future versions (0.30+),
I said I was going to package a Mac version as well, but I'm not there yet.

I had at least one guy (Hummingbird, back on page 37) that got a Mac
version to work. He said he had to copy shader.vs and shader.fs from
the Mac package from a separate download (because I removed them
from the PC version because I thought they were unnecessary). They
will be left in all future versions, but for now see if adding those helps.

[Hummingbird]

For Ironhand tiles on Mac:

I've found that it's definitely simplest to copy the raw, art, and init folders from the Ironhand DF into your Mac DF folders. This has worked with each version of Ironhand that I've tried thus far.

Just drag the raw folder from the Ironhand folder into the Mac version's main folder, and the art and init folders from the Ironhand data folder into the Mac data folder. This way you get to have the same DF folder across different versions of Ironhand, and you don't have to copy any saves.

Hope this helped.