Cryengine 3 free finally available
-
Pichuneke's color blinded forest.
It's a beginning...
-
Strawberry Fields Forever
-
@pichuneke said:
Pichuneke's color blinded forest.
It's a beginning...
So, does one do a walk through with a shotgun/machine gun?
-
@solo said:
@pichuneke said:
Pichuneke's color blinded forest.
It's a beginning...
So, does one do a walk through with a shotgun/machine gun?
I think that it can be changed... with work, and learning...
At this moment I am fighting with PlayUp tools, I even can't make it work
-
Hi,
At the moment I am struggling even with the tool PlayUP. I've read through the tutorial again. But only two files are created, mtl and dae. I suspect that that is somehow connected with the path settings in the preferences or a bug because the context menu commands are grayed out.
Charly
-
The whole tutorial confused me a bit!
-
I did it again with another SKP model. Now the files were created as shown in the tutorial. In the Cryengine it does not appear anyway.
-
Charlie, I asked for help in the official Facebook page.
You should try:
<PATH TO CRYENGINE DIRECTORY>\Game\Levels\YourLevel\By the way, for technical help you should suscribe to PlayUp Tools facebook page:
Ah, and new version available now.
-
@charly2008 said:
The whole tutorial confused me a bit!
The tutorials were written for Crysis 2 SDK, not standalone SDK. These are basically two slightly different branches of the same engine and toolset, and while the workflow is 99% similar between them, some parts still differ. I mentioned that every time, check the gray notes.
Now that the CE3 SDK is released, the tutorials will be updated to match it, shortly.
Regarding terms of use of these two: basically, Crysis 2 toolset can be used for any non-commercial project (you just need to own Crysis 2 copy in order to be able to install the toolset); but it is slightly less flexible in some specific features (Flowgraph scripting, command line variables availability, etc.), so it's used primarily for modding. For standalone projects, from architectural visualizations to full-fledged games, new CryENGINE 3 SDK is a better choice. It will be regularly updated, it's featuring source code access, better tools and so on. At the moment in can be used only for non-commercial projects, but licensing options will arrive shortly and are believed to be similar to UDK (royalty-based licensing for small commercial projects).
Though I'd like to warn you that current release of standalone CE3 SDK is somewhat buggy, as it's only the first one. Over time all the errors should be fixed (just like it was with the UDK), but maybe it'll be better to wait a bit until more stable release arrives. If some of you own a Crysis 2 copy, and are willing to practice things irrelevant to toolset differencies, e.g. model export or simple mapping, I'd suggest to practice in Crysis 2 SDK for a while, as it is more stable at the moment.
Upd: I've updated the tutorials:
http://www.crydev.net/viewtopic.php?p=830043#p830043Be sure to download the latest version of PlayUp Tools.
-
I made a fast video:
As usual, I can't deal with the Flash tag, if someone wants to see it here, feel free to insert the video in your comment.
All the imported models in Cryengine 3 have the following limitations: 65.000 polygons and 32 textures per model. But you can import many of them to avoid these limits.
PlayUp exports different components as separate entities. I don't know if there is a way to put all together in their right position at once, doing it individually is not viable for me. So in the video I have placed two big elements of my model of the roman theatre of Orange by hand. No collisions yet, I am a ghost that can walk through the walls
bac9-flcl: Thanks for your work. I am sure that you know how to deal with my problems, but I am a newbie and I am learning
-
@unknownuser said:
At the moment in can be used only for non-commercial projects, but licensing options will arrive shortly and are believed to be similar to UDK (royalty-based licensing for small commercial projects).
Well that's a problem, most of what I do is commercial, unless I'm playing around, so what's the point in taking the time to learn this app if I cannot use it for a visualisation render/animation? Do I need to negotiate my fees with a percentage allocated to Cryengine?
-
@pichuneke said:
All the imported models in Cryengine 3 have the following limitations: 65.000 polygons
I'm sure it's rather 64.000 vertices. Polycount is rather irrelevant as it can vary from ~30.000 to ~120.000 depending on a mesh configuration.
@pichuneke said:
PlayUp exports different components as separate entities.
Yes, if your model is consisting of several components and groups on the top level of hierarchy, after using "Export All Components and Groups" action, you'll get several models. You can combine the whole model into the new parent component if you want to export it as the solid object. However, you should be careful with that due to risk of problems with vertex coordinates precision. If an object is huge and contains quite small details at the same time, it's recommended to split the model into several pieces. Check the tutorial section 6.4 for explanation on vertex precision and 3.3 for tips on the subject of proper component structure.
@pichuneke said:
I don't know if there is a way to put all together in their right position at once, doing it individually is not viable for me.
You should keep an eye on the position of pivot points (axes origin points) in each of the parent components you intend to export. Use Change Axes context menu action in SketchUp (available inside Edit Component mode) to relocate them properly.
If you want to assemble the building in the engine, all the pivots of used components should be located in the same area: this way the building can be easily assembled by specifying the same coordinates for each and every part. But well, you can have the same result by just combining the whole model into a single parent component.
However, in case of a huge object, having the same pivot position for all parts sometimes makes the 16-bit range of values extremely insufficient to properly describe all the vertex positions in the distant areas of the model. Not to mention that it's very inefficient to have a pivot positioned e.g. 50 meters away from some wall component, as in this case not even a half of possible values is available for vertex description.
In case of a huge object, if you think that you'll probably get damaged results with exporting the whole model at once, I recommend to use parts. Most importantly, you'll need a different pivot for each part, to make sure that vertex position precision is as best as possible for each of them. And in order to be able to reassemble the whole object in the editor, you'll need to place these pivots on some regular grid (for example, on the same height and with 1 meter snap). Draw a grid with Sandbox SketchUp tools, it'll be helpful when you'll use the Change Axes mode.
Then all you'll need in the engine Editor will be to switch on the snapping, grab the Move tool and assemble the model. With proper pivots, it'll be easy and precise.
-
@solo said:
@unknownuser said:
At the moment in can be used only for non-commercial projects, but licensing options will arrive shortly and are believed to be similar to UDK (royalty-based licensing for small commercial projects).
Well that's a problem, most of what I do is commercial, unless I'm playing around, so what's the point in taking the time to learn this app if I cannot use it for a visualisation render/animation? Do I need to negotiate my fees with a percentage allocated to Cryengine?
There is another good engine, UDK. You can use it free until 50.000 dollars, I believe.
But I have no too much experience with that engine. To me, the use is too complex. But as I do my models for free, I looked at Cryengine... (because it's a hobby).
Anyway if you try UDK, and you make progress with it, let us know, please.
-
@bac9-flcl said:
@pichuneke said:
All the imported models in Cryengine 3 have the following limitations: 65.000 polygons
I'm sure it's rather 64.000 vertices. Polycount is rather irrelevant as it can vary from ~30.000 to ~120.000 depending on a mesh configuration.
@pichuneke said:
PlayUp exports different components as separate entities.
Yes, if your model is consisting of several components and groups on the top level of hierarchy, after using "Export All Components and Groups" action, you'll get several models. You can combine the whole model into the new parent component if you want to export it as the solid object. However, you should be careful with that due to risk of problems with vertex coordinates precision. If an object is huge and contains quite small details at the same time, it's recommended to split the model into several pieces. Check the tutorial section 6.4 for explanation on vertex precision and 3.3 for tips on the subject of proper component structure.
@pichuneke said:
I don't know if there is a way to put all together in their right position at once, doing it individually is not viable for me.
You should keep an eye on the position of pivot points (axes origin points) in each of the parent components you intend to export. Use Change Axes context menu action in SketchUp (available inside Edit Component mode) to relocate them properly.
If you want to assemble the building in the engine, all the pivots of used components should be located in the same area: this way the building can be easily assembled by specifying the same coordinates for each and every part. But well, you can have the same result by just combining the whole model into a single parent component.
However, in case of a huge object, having the same pivot position for all parts sometimes makes the 16-bit range of values extremely insufficient to properly describe all the vertex positions in the distant areas of the model. Not to mention that it's very inefficient to have a pivot positioned e.g. 50 meters away from some wall component, as in this case not even a half of possible values is available for vertex description.
In case of a huge object, if you think that you'll probably get damaged results with exporting the whole model at once, I recommend to use parts. Most importantly, you'll need a different pivot for each part, to make sure that vertex position precision is as best as possible for each of them. And in order to be able to reassemble the whole object in the editor, you'll need to place these pivots on some regular grid (for example, on the same height and with 1 meter snap). Draw a grid with Sandbox SketchUp tools, it'll be helpful when you'll use the Change Axes mode.
Then all you'll need in the engine Editor will be to switch on the snapping, grab the Move tool and assemble the model. With proper pivots, it'll be easy and precise.
Thanks for your long answer. I'll try to use it as a reference to import some of my models next week. I'll let you know how I am doing it
-
@solo said:
@unknownuser said:
At the moment in can be used only for non-commercial projects, but licensing options will arrive shortly and are believed to be similar to UDK (royalty-based licensing for small commercial projects).
Well that's a problem, most of what I do is commercial, unless I'm playing around, so what's the point in taking the time to learn this app if I cannot use it for a visualisation render/animation? Do I need to negotiate my fees with a percentage allocated to Cryengine?
It is a difficult question, and first of all I'd suggest asking Crytek directly about the conditions of engine usage for commercial architectural visualization. Maybe they have already licensed the engine in the similar cases. Check mycryengine.com for contact details.
As about public licensing conditions and that new free SDK, I believe that licensing details for it are still being worked out. And I'm afraid that, as this SDK release is primarily targeted for indie game developers, licensing options for commercial architectural visualization won't be published as soon as ones for game developers. Perhaps that will have to wait.
The toolset is still in a very early stage of evolving comparing to UDK, but eventually that should be figured out. Here's the quote from UDK licensing conditions.
@unknownuser said:
An architecture firm uses UDK to create a live walk-through presentation for their customers. They charge their customers a fee of US$500 for each walk-through. Before they begin to charge customers for the walk-through, they would pay Epic US$99 for a royalty-bearing commercial UDK license. They sell walk-through presentations to 100 customers in the first quarter, bringing in US$50,000 in revenue. No royalty payment would be required to Epic for that first US$50,000. In the second quarter, they sell another 100 walk-through presentations, bringing in another US$50,000 in revenue. They are required to pay US$12,500 to Epic. On subsequent revenue, they are required to pay the 25% royalty.
Note that they do not charge royalties until revenue reached more than 50.000$, it's a general rule for all kinds of projects. Royalty conditions for commercial architectural visualization are even slightly easier then the ones for game developers.
I believe that, as Crytek wants to compete with UDK, they will eventually arrive to similar licensing conditions.
On the side note, UDK is more powerful at the moment as the game development toolset (that's quite natural as it's been around for more than two years), but I'm not so sure about visualization. UDK content pipeline is harder to learn than the one Crytek is utilizing, and the lighting system of CryENGINE 3 is for sure much more powerful than Unreal Engine one (availability of real-time Global Illumination, real-time screen space reflections, hundreds of light sources on screen with decent fps, LUT color correction, extremely powerful atmospheric lighting system, and so on).
-
PlayUp has had a great update!
New PlayUp Version Available with CryENGINE Fixes
SketchUp plugin that allows people to create and export content to a 3D game engines such as Unity 3D, Crytek CryENGINE, and Valve Source
(playuptools.blogspot.com)
This will make the process much more straightforward
@unknownuser said:
Now, whether you're in SB2, SB3 or the CE3 Standalone SDK, your material paths in the MTL files will be pointing to the right place. You should no longer have to reassign materials in the Material Editor. Also, if you apply SketchUp colors instead of textures, it will no longer look so washed out in CE3.
-
Hi Michael,
The new file shows still version 0.9.8.0?
Charly
-
Another video:
All the theatre exported, some glitches (I had to position some parts manually, and I made it all very fast). I prefer not to talk about textures, yet.
-
@unknownuser said:
@unknownuser said:
So, does one do a walk through with a shotgun/machine gun?
That doesn't take much effort to remove at all. Can't remember how but I worked it out in a minute or two the other day.
Also I'm not sure about the file still showing .0
Maybe playups dev forgot to change itPichuneke, cool video, you should throw on some textures I think it'd look cool
-
PlayUp update released!
version 0.9.8.2http://playuptools.blogspot.com/2011/08/first-pass-at-cryengine-3-level-export.html
Featuring level export and various improvements in other areas!Be sure to use it.
Advertisement