Hi Tenno,

Quick note for those of you working on a Warframe helmet right now: we're increasing the maximum tri count!

A lot has changed in Warframe in the past 3.5 years that TennoGen has been around, including more complex helmets and Warframes. So, to reflect the added complexity -- including FX and cloth details that you have with Warframes like Revenant and Wisp -- we are increasing the Alt Helmet tri count from 5000 to 8000. The guides have been updated, so this change is in effect immediately. 

Thank you for your continued support and feedback

On 2019-07-08 at 1:15 AM, (PS4)The_Verethragna said:

I just noticed that the tail on Wukong's Mithra skin has been changed to be the exact same as that of the Auman skin, both by different creators and neither being the same tail as the base model.

Thanks, looking into this now!

The Tatsu is finally TennoGen-ready!

This weapon is par for the course with other swords, but it does have the added fun FX. FX is not mandatory, but if you want to include custom FX, we have outlined the instructions below:

The FX on this sword are shared with the Revenant. The textures themselves cannot be changed, but the main texture used in this FX is provided for your reference. If you would like to add custom FX, please make sure to match the new weapon to the Eidolon/Sentient theme. Don't add FX tendrils to other factions.

Setting up the FX:

• Use the default FX cards on the default Tatsu weapon as reference. Match your custom mesh's
• UVs to these default cards. Making the UV islands larger or smaller will change the scale of the textures that are applied to the geometry.
• Test the result in the TennoGen viewer. Get the scaling of the textures to roughly match the default FX scaling by editi...

For TennoCon 2019, we continued the tradition of announcing new content during our  that we’ll be bringing to the program this year -- but with a bit of a twist! Skyers and Kaz both live modelled some of the new content types we announced. 

While we can’t share the full workshop, we can share what was discussed and revealed (as well as the concepts I tortured them into making a reality).

Let’s get right into it!
 

New Factions

Since October 2015, TennoGen creations have been loosely tied to the four core Warframe Factions: Tenno, Corpus, Grineer, and Infested (and their various sub-factions).

Warframe has grown a lot since 2015, and so it’s time to expand the Factions for the creators and the community! Expect these new Factions to appear in our Faction Style Guide hopefully soon:

Ostron

Solaris

Sentient

Dual-Ha...

On 2019-06-11 at 7:06 PM, EmberStar said:

Octavia's Mithra skin is applying the Energy color to her helmet ponytails and to the Madachord arcs on her main body.

Revenant's ghost-fire plumes are also taking their color from his Energy color, in addition to still being really bright.  Before the changes to Emissive and Energy, the ghost plumes were fainter and more ghostly looking.  Now you can't even see the geometry of his left arm at all with the default colors.

This is intentional! FX is set up to use energy colour, emissives use emissive colour. The difference wasn't obvious when emissives and energy used the same channel for colours, but the distinction between the two is a result of how skins are set up.

On 2019-06-11 at 7:06 PM, EmberStar said:

Last time I checked, Trinity Prime's helmet is not properly sharing the Emissive channel with the rest of her body using the default colors.  When I checked, her faceplate w...

On 2019-06-06 at 8:58 PM, Demeraire said:

Garuda successor skin talons have been broken for months as a client. It has a similar problem to khora mithra. Please take a look into this problem.

On 2019-06-06 at 6:03 AM, miramiranda said:

The new Aures skin for Nyx  seems bugged. It is impossible to change the colors of the "feathers" (by the ears). You can pick another color but soon as you save, it reverts back to the original purple.

Tried to submit a screenshot, but apparently you can't do this (only URL links and I don't know how to do that)

On 2019-06-06 at 11:00 AM, zValor said:

On the new khora mithra a full cycle of venaris modes breaks the visual changes to khora and it goes back to default when it should look like this. https://sketchfab.com/3d-models/khora-mithra-t-pose-a7efb7e3c65040daa87ca511ccec483e

These have all been reported to the team, thank you for sharing them here! I d...

2 hours ago, TheLastOfFallen said:

I have been having a bug with the Lympharis polearm skin where status effects are about 3 feet away from the blade and since the latest tenogen additions the energy is always default regardless of what is chosen.

This just happened on Dani's stream - what a coincidence! Also will be passing this on, thanks!

3 hours ago, gekkougabutt said:

Ah I think I get it, if I'm understanding this right the reason this skin wasn't accepted is the fact it was a Corpus themed skin outside Corpus design aesthetics. Well now I'm super curious as to what would've happened if the artist never gave any hint of their Solaris inspirations, and just marketed it as a "Cyberpunk" themed skin or something, if it would've still been denied by DE if there was no Corpus attachment stated or not. 😮

There were a variety of factors that resulted in us not being able to consider it for Round 16, unfortunately. Marketing of an item has little way on the team's decision, since it is grounded in technical and style guidelines. 🙂

Quick update for clarity!

21 hours ago, [DE]Taylor said:

Wisp’s helmet textures in-game are much larger than usual -- 2048 x 1024 VS 1024 x 512. [...] If you decide to make a cloth-less helmet, the helmet resolution is then limited in-game to 1024 x 512.

The larger resolution is for in-game instead of authored. You can author your pieces at 4084 x 2048 if you wish (for those with cloth). Clothless helmets will use the regular authored 2048 x 1024 and in-game 1024 x 512 resolutions. Sorry for any confusion here!

Wisp Files are officially available in the Steam Workshop! 

Much like Revenant, she is made using new tech, so there are some missing textures in her ZIP file. It’s on you as the creator to make these maps yourself without any reference files.

Below is a list of what is included in the ZIP: 

• Normal
• Emissive
• Tintmask
• Body and Helmet meshes

To be clear, you are expected to still make the specular, roughness, and diffuse maps -- we simply can’t send you a reference for comparison.

IMPORTANT NOTES ABOUT CLOTH:

Wisp’s helmet textures in-game are much larger than usual -- 2048 x 1024 VS 1024 x 512. This is because of the extra mesh that extends down her front and back to form a cowl. You are not obligated to include draping cloth along her back and/or front for your helmet, but if you decide to make a cloth-less helmet, the helmet resolution is then limited in-game to 1024 x 512.

The polygon count is still limited to 5000, even with...

We’re back with what possibly is the last stream before TennoCon 2019. The team has come with their hands full of reveals and updates before we prepare for our radio silence. You can learn more about the 41st Warframe, our plans for a Wukong rework, a peek at some sentient tilesets in the works, either by reading our overview here: https://www.warframe.com/news/devstream-128-overview

7 hours ago, Vlada91 said:

I just don't understand 1 simple thing,if we did seen tennogen skins on last devstream. Then why we can't have it already in the global build,why we need to wait for another month, and not having right now in the game why DE???? 🤔

Setting up the files to showcase on a Devstream is different than getting them hooked up properly for sale in-game -- we need to set them up in the market, set up rigging (for Syandanas/helmets/etc.) and FX. And then it needs to be all tested. 🙂

That takes time, especially for multiple items, in addition to all the other amazing things our team is working on. Thanks for your patience!

3 hours ago, [DE]Taylor said:

UPDATE: 7:40 PM EDT

Microsoft has informed us that the issue should now be resolved -- after testing, that appears to be the case. Thanks again for your patience. 🙂

We have heard back from Microsoft that the issue should be resolved. If you are still experiencing issues, please restart your console and you should be able to connect.