Need Developers opinion about asset packs!

[Michael Betke]

I'm putting together some new vegetation packages at the moment and I'm at the point to choose between offering one big pack with three or fours specimen in one pack.

My other consideration is to split the large pack into several ones which cost not so much, so instead of offering 30 tree models in one pack I would offer three packs with 10 trees in it (10 birch, 10 pines, 10 trunks and so on).

[Mumbles]

I'll only pay for exactly what I want... That's usually tailor-made packs. Price I would normally leave down to the person making the pack - it is their hard work after all... Provided it's not too expensive I would normally pay, but only if it has everything I want. Anything missing and I normally won't go for it...

[Josh]

I think you might do best by offering several lower-priced packs, and one big one that costs less than the sum of the others. If you can automate the ordering process, selling each individual asset might not be bad, at a much higher price per item relative to the complete pack.

[DaveLee]

I'm a big fan of more options. At work we've purchased tree sets before, and it's frustrating when you have to buy 10 trees that you don't want to get the 12-15 trees that you do want. My vote is for smaller packs that give users more options (priced accordingly) along with a "Full package" option that has everything, maybe with a 10% discount compared to purchasing all of the smaller packs individually.

[Jardar]

I aggree with the above, smaller packs are easier to buy because you know all the better what you get. Then you can pick and choose from the assets which is so easy to do when you know you only pay for what you want to have. So I say, smaller more specific packs

[Michael Betke]

Thanks guys. This is what I also thought. Means more work for me to manage the orders but also a faster release cycle for new packs.

After I hit one "milestone" I'll offer a Super-Bundle with more combined stuff in it.

[Rick]

Build your own pack! Nuff said.

[Joh]

Well, this is an hard question..

I always prefer to work with a 3d artist on my team, but if i should choose, i will surely choose to buy a big pack of my own choise, obviously this will cost me more, also i'll never allow you (or who created the pack) to re-use my models, but i think we are just a few that thinks in this way..

[Raul]

The Bundle editions sounds good. Also would be interesting if we would be able to choose what models to buy

 

I mean I would like to take the trees from Nature Pack #3 and the Streets from Urban Package #1

[Michael Betke]

Yes RVL I thought about the same some time ago. But I don't have time/resources or knowledge to do this. Would require a complete shopsystem and I still want to concentrate on contract work and not asset selling.

[Raul]

I see. Anyway your assets are gorgeous from what I saw in the PDF so good luck. I will also buy some packs in the future thats for sure

[gamecreator]

Yeah, choosing your own assets would be the ideal way to go, with discounts for buying in quantity. The next best option is offering both smaller packs and larger packs (all trees, all forest items, etc.).

[DaveLee]

If I could offer another suggestion - it might be a good idea to offer some kind of downloadable "sample tree" without the .max source files. It could be hard for people to tell from the PDFs how high quality the assets actually are.

[Michael Betke]

Yes absolutly. There will be a even better solution to this very soon. You will be able to take a tour ingame and see the trees.

Just waiting for the App.

[Leo]

I think you might do best by offering several lower-priced packs, and one big one that costs less than the sum of the others. If you can automate the ordering process, selling each individual asset might not be bad, at a much higher price per item relative to the complete pack.

I totally agree. It's what people usually do when selling assets on sites such as 3D02 or The3DStudio.

 

The large pack aimed at people who wants to build a library of resources, and smaller ones to developers which only need to fill a gap (for example, I usually do trees with Pawel Olas' Lightwave plug-in, but could benefit from borrowing plants and rocks).