CRYENGINE 3.8.3 Released
Subscribe:  iCal  |  Google Calendar
7, Mar — 12, Jun
San Francisco US   19, May — 24, May
London GB   29, May — 1, Jun
Birmingham GB   1, Jun — 4, Jun
Taipei TW   5, Jun — 10, Jun
Latest comments
2 hours ago

Derjyn it is really hard to understand your motivation of commenting. I bought the material and it *highly* satisfied my needs. Also the seller is really helpful, I was'nt able to run it in 4.18 he fixed it in minutes. If you really want make something really productive create your material and than release an article here.

by Alex
3 hours ago

So uhh.. What's happening at Machine Games then?

3 hours ago

Great article but the link to the artist's Artstation portfolio is no longer working?

CRYENGINE 3.8.3 Released
9 September, 2015

CRYENGINE 3.8.3 has released and although there aren’t a lot of features, there are plenty of fixes and optimizations.

Some updates:

Character Attachment Merging (Shadows)

CRYENGINE characters consist of many attachments tied together via the skeleton. Although this approach provides much flexibility which makes rendering quite expensive as each part needs to be rendered individually. Shadow rendering has been optimized to where all attachments are merged into a set of large meshes that can be rendered with one draw call each.

UV Mapping Editor

This allows for more easy and powerful ways to define UVs of a designer object, quite similar to what could be built in most DCC tools. This is a list of some of the important changes made:

  • New: Improved occlusion and indirect shadowing quality.
  • New: Added two new Lightstyles (49/50) to simulate large and small open flame variations.
  • Fixed: SplineDistributor can be hidden now.
  • Fixed: New level – on creation, make an objectives.xml. Removes warnings in editor log.
  • Fixed: Cubemap generation when SVOGI is in use.
  • Fixed: CUIEntityTag first-frame flickering.
  • Tweaked: Changed Vegetation Tool “UseSprites” checkbox to be unchecked by default. Sprites are no longer supported.
  • Tweaked: only brushes need to notify the NavMesh of upcoming changes of their AABB.

The full list of fixes and implementations can be found here.

Leave a Reply

Be the First to Comment!