News for hackers. Stuff that matters.
Re:CopperSpice, a Modern C++ Fork of Qt by IshKebab on Tuesday June 09, 2015 @07:43AM (#9685253)
There are some downsides to Qt5.

* It's huge - something like 30 MB for "hello world" on Windows.

* Deployment is a nightmare (loads of plugin DLLs, there's some crazy path stuff going on, if you use QML you have to include a load of system qml files). There is a windeployqt tool which helps but it still isn't as easy as with Qt4.

* QML/QtQuick are very nice for some things, but in a lot of ways they kind of suck. E.g. passing data between C++ and Javascript is always a pain. Also most of the QML tools (compiler, usable GUI editor, profiler, etc.) are only in the enterprise version of Qt.

Having said that, I don't know why they didn't just base it on Qt5, remove all the QML stuff and make unicode optional (unicode support costs about 20MB). Qt5 already uses C++11 syntax for signals and slots (though you still need moc).

I don't know why you dislike their website.

Re:CopperSpice, a Modern C++ Fork of Qt by coldtea on Tuesday June 09, 2015 @09:07AM (#9685642)
>It's huge - something like 30 MB for "hello world" on Windows.

First, 30MB for "hello world" doesn't mean it will get linearly bigger as code grows. Most is one time off overhead. Else something like Kate would be an 1 TB binary.

Second, 30MB hasn't been an issue since 2002. Heck, I have 20+ apps, each over 30MB, on my PHONE.

Re:CopperSpice, a Modern C++ Fork of Qt by nadams on Tuesday June 09, 2015 @10:19AM (#9686028)
> Second, 30MB hasn't been an issue since 2002

Back in 2004 a demoscene group created a FPS in 96kb - http://www.pouet.net/prod.php?which=12036

That 96kb includes textures, engine and music. No they aren't downloading content or streaming from the internet. I know how they did it - and with some tweaking of gcc command line parameters you can write C you can get close to those file sizes.

When I see that the game RAGE, while an excellent game, takes up 20GB of disk space I just shake my head. Now I'm not advocating that everyone should be making FPSes at 96kb - but I feel like 20GB is a little unnecessary for the game RAGE (especially how short it was).

I personally try to be as efficient as possible when it comes to using other people's storage and memory.

Re:CopperSpice, a Modern C++ Fork of Qt by scrollaway on Tuesday June 09, 2015 @10:25AM (#9686075)
That is a phenomenally ridiculous comparison. They are doing procedural textures/audio etc. RAGE is 20GB because it has a massive amount of high resolution textures, meshes and audio.

Nothing to do with the libraries they use.

[deleted]
Re:CopperSpice, a Modern C++ Fork of Qt by SEMW on Tuesday June 09, 2015 @11:06AM (#9686334)
> games should do procedural terrains

The decision between prerendered and procedurally generated terrain/textures/etc. is a tradeoff between.. oh, I dunno, developer time, artist time, platform disk space, download time, platform CPU usage, platform graphics usage, and other factors. If you believe game studios have been consistently going for the less optimal choice, then you or someone else could start a studio that makes the better choice, exploit that inefficiency, and gain a market advantage. (Perhaps the demographic of gamers with modern CPUs but 1990s hard drives is ripe for tapping?).

If on the other hand there is no such market potential, then it isn't clear to me in what practical sense the assertion that games 'should' be procedurally generated holds.

Re:CopperSpice, a Modern C++ Fork of Qt by Qwertious on Tuesday June 09, 2015 @12:02PM (#9686672)
So, now you need your artists to be programmers.

I don't think you quite understand what you're asking. The number one rule for high-quality aesthetics in games is that you let the ARTISTS call the shots, with someone in-between to tell them when that's a terrible idea technically. This would break that horribly.

And that's ignoring the load times, which increases massively if you have to procedurally generate it. And having decent level design, which I GUARANTEE will not often pop up naturally in procedurally-generated environments. Meanwhile, disk space is pretty damn cheap and will save you a bunch of time and money.

Re:CopperSpice, a Modern C++ Fork of Qt by nadams on Tuesday June 09, 2015 @02:59PM (#9687887)
> So, now you need your artists to be programmers.

There is some arguments if you should allow artists to program (Blender does have a built in scripting language).

However, the same group that created the FPS demo also created a tool to create demos - artists can go as wild as they want without needing to write a line of code: http://www.farbrausch.com/prod.py?which=168

If you want something a little more well documented and updated you should check out ZGameEditor - http://www.zgameeditor.org/.

> And that's ignoring the load times, which increases massively if you have to procedurally generate it.

Any reason why you can't render and save the textures on first run? I feel like Natural Selection 2 does that.

> Meanwhile, disk space is pretty damn cheap and will save you a bunch of time and money.

You are forgetting the step in between. Using your argument that disk space is cheap (and assuming they don't use their hard drive to store anything else...) - in the US ISPs are playing a dangerous game. A small DSL provider has a 5GB cap and will charge outrageous fees for going over: http://stopthecap.com/2010/04/14/frontiers-5gb-cap-is-back-n...

Downloading that 20GB RAGE game has turned into quite a challenge (of course you could always use the Valve response of "take your computer to a friends house").

Re:CopperSpice, a Modern C++ Fork of Qt by scrollaway on Tuesday June 09, 2015 @11:24PM (#9689886)
Here's the thing: Procedural rendering is a tool. It's useful in some cases (like, say, randomly generating massive universes with distinctive patterns a la elite, minecraft, etc). It's useless if you want to do predictable things which obey a designer's vision. Going from concept art/blueprint to a live mesh is completely impossible with the tooling we have today to do procedurally.

Yes, most games could certainly optimize their contents. I'm certain there's dozens of gigabytes of data which could be shaved off on any gamer's computer between all the installed games, but most of what's in there is there for a reason. Also ... something about frying fish.

So treat that technique as a tool. Not everything is a nail. Is RAGE too large? Maybe. Would procedural generation be appropriate for it (in a way that meaningfully reduces contents size)? Certainly not... not without redesigning the game from the ground up.

Re:CopperSpice, a Modern C++ Fork of Qt by artificial on Tuesday June 09, 2015 @08:35PM (#9689419)
>Downloading that 20GB RAGE game has turned into quite a challenge Dated First World problems notwithstanding I immensely enjoy the harping on RAGE, especially the fixation on the assets (and the resulting download size). GTAV is nearly 60GB and is immensely popular. It uses a traditional texture model compared to the Megatexture technique used in idtech. Computing the quantity of textures on install would result in people remarking how long it takes to install instead of download.

> You are forgetting the step in between. Using your argument that disk space is cheap (and assuming they don't use their hard drive to store anything else...) in the US ISPs are playing a dangerous game. A small DSL provider has a 5GB cap and will charge outrageous fees for going over Canadians have been dealing with dinky quotas for awhile and entertainment streamed or downloaded thrives there. In the states there are plenty of people on dial up who live out in the sticks or are on satellite connections and you know what? I'd wager these people aren't the target market. For the vast majority of businesses the most expensive thing is employee overhead. Storage is cheap and getting cheaper, developer time not so much. I appreciate technical efficiency as much as anyone. The reality is that the junk pile is full of technically superior products that died because the competition beat them to market or out marketed them.

>However, the same group that created the FPS demo also created a tool to create demos - artists can go as wild as they want without needing to write a line of code: http://www.farbrausch.com/prod.py?which=168 If you want something a little more well documented and updated you should check out ZGameEditor - http://www.zgameeditor.org/. Neat. I'd sincerely enjoy seeing an attempt at making a game like RAGE with zgameeditor. I see excellent examples of toy tools. Using the right tool for the right job makes a world of difference, take a look at Unreal4, ZBrush, Maya, and a host of others involved in asset pipelines. You'll notice many of these tools are specialized. Pay close attention to the features and compare those to zgameditor.

Re:CopperSpice, a Modern C++ Fork of Qt by vezzy-fnord on Tuesday June 09, 2015 @10:20AM (#9686032)
Heck, I have 20+ apps, each over 30MB, on my PHONE.

I don't recall most smartphone OS being well known for intelligent resource utilization.

Re:CopperSpice, a Modern C++ Fork of Qt by ci5er on Tuesday June 09, 2015 @07:43PM (#9689265)
> Second, 30MB hasn't been an issue since 2002. Heck, I have 20+ apps, each over 30MB, on my PHONE.

Good for you?

That doesn't mean that it is not an issue.

Re:CopperSpice, a Modern C++ Fork of Qt by coldtea on Wednesday June 10, 2015 @04:21AM (#9690650)
>That doesn't mean that it is not an issue

When I said "I have 20+ such apps on my PHONE" my intension wasn't to imply I was some lone outlier having those. Rather, that this is the NORM for anyone with a smartphone today.

So, if a billion people are OK with 20+ 30MB+ apps on their phones, it does mean it's not an issue -- and even less so on the desktop, which has 10x or more the storage capacity of a smartphone.

Re:CopperSpice, a Modern C++ Fork of Qt by IshKebab on Wednesday June 10, 2015 @07:59AM (#9691377)
Of course it doesn't grow linearly, but 30 MB is a huge up-front cost. If you're writing a simple app - or even a relatively complex one - users on slow connections will be a bit annoyed.

A basic Qt text editor is about 5 times the size of Notepad++. That isn't good. And yes I know why that is the case but that doesn't really excuse it.

Re:CopperSpice, a Modern C++ Fork of Qt by purerandomness on Tuesday June 09, 2015 @11:03AM (#9686310)
How large do you think is a "Hello World" app that uses .NET?
Re:CopperSpice, a Modern C++ Fork of Qt by Qwertious on Tuesday June 09, 2015 @12:05PM (#9686686)
Well, considering that anything that uses .Net will by definition have .Net as a dependency, at least the size of .Net.
Re:CopperSpice, a Modern C++ Fork of Qt by IshKebab on Wednesday June 10, 2015 @08:01AM (#9691388)
.Net apps don't usually bundle the runtime with them. Qt apps have to.
Re:CopperSpice, a Modern C++ Fork of Qt by joezydeco on Tuesday June 09, 2015 @11:22AM (#9686442)
When you begin to get serious about app size using Qt (especially when you're on embedded) you configure and compile the libraries from scratch instead of pulling the SDK libraries in.

I can typically get under 6MB on ARMv7. Nothing to brag about, but if you want a demoscene-sized app targeted for a single architecture you aren't using Qt anyway.

Re:CopperSpice, a Modern C++ Fork of Qt by IshKebab on Wednesday June 10, 2015 @08:02AM (#9691395)
Yeah... that is a pretty huge pain though. Also there are more licensing issue with static linking - you have to distribute the .o files etc.
Re:CopperSpice, a Modern C++ Fork of Qt by scrollaway on Tuesday June 09, 2015 @08:05AM (#9685351)
QML/QtQuick etc are modules in Qt 5, you don't have to depend on them at all and they're not linked in. QtCore is tiny.
Re:CopperSpice, a Modern C++ Fork of Qt by mmozeiko on Tuesday June 09, 2015 @01:10PM (#9687123)
Afaik if you don't need WebKit then you can disable icu when building Qt - use "--no-icu" when running configure. Not sure exactly how much it will disable, but it will free you from depending on icu libraries for core libraries