Latest
Top Viewed
Top Rated
Controller. Offline? Starcitizenlauncher.exe Agree Thrustmaster Login Paysafecard Hardware Rifles Sweet
Add +
Member Since []
[OP] 127 views 0 replies Posted by Unknown 9 years ago Mar 29, 2:49 am forums.robertsspaceindustries.com
Hey fellow CryEngineers!
I wanted to do a quick write-up of issues that you guys may be starting to come across with the new variant system that CIG is starting to push out in the public builds of Star Citizen that Travis Day talked about in the most recent episode of Around the Verse.
The variants are now essentially “body kits” that get attached to the ships. Below is a picture of the Aurora Base Model with the variants. From left to right they are Base, LX, LN, CL and MR.
As Travis day was explaining this is EXCELLENT from a development and gameplay perspective because it allows them to use a unified skeleton of sorts where they only need to push an update once time instead of updating each of the ships that would have its own geometry and properties. The ships are now using an XML file they are using in the scripts that calls for changes to be made based on the variant requested by the game. Attached here is an image of the XML file that is calling for the 315p and 325a.
This comes with a nasty side effect for us working in the CryEngine SDK at the moment, and that is we really have no real way to get these variants working for cinematic sequences. CIG has we all know heavily edited CryEngine and this includes adding custom classes and other code to get spaceships working. They use a Vehicle entity for in game stuff but when we do cinematics we need to use a Physics/AnimObject entity for track view animations. The issue for us is that we do not have a way to call on these modifications as we would if we were using a vehicle entity.
Here are a few images showing the best I could come up with after ******** around for an hour or so. I used the character editor and attached the 325a “body kit” to the base 300i and saved it out as a .cdf to call back into the editor as an AnimObject to use in a sequence. I originally planed to showcase the 325a in a video I was going to make this weekend now that it’s available in arena commander.
Besides the layering issue there is also a hard set issue on the 325a’s bodykit not animating which totally ruins it for fan-made sequences. The same goes for the Aurora variants and it's starting to show up with the Hornet as well and is assumed to follow suit with anything else in the pipeline.
This isn’t a write up with a solution, sorry. I just wanted to make it known out there for fellow modders/video makes that Variants are FUBAR’d ATM and I don’t see it getting better until we get an official Star Citizen SDK. I will keep trying to see if I can’t get things to work properly but I wouldn’t hold my breath. I only have about a month’s worth experience playing with the SDK and I am still learning a lot. If anyone here knows more than I, (a devs input would be AMAZING) and has any input on this issue feel free to share your thoughts and ideas.
PS: If you guys don’t see any videos from me for a while, this is why just as a heads up! ;)
I wanted to do a quick write-up of issues that you guys may be starting to come across with the new variant system that CIG is starting to push out in the public builds of Star Citizen that Travis Day talked about in the most recent episode of Around the Verse.
The variants are now essentially “body kits” that get attached to the ships. Below is a picture of the Aurora Base Model with the variants. From left to right they are Base, LX, LN, CL and MR.
As Travis day was explaining this is EXCELLENT from a development and gameplay perspective because it allows them to use a unified skeleton of sorts where they only need to push an update once time instead of updating each of the ships that would have its own geometry and properties. The ships are now using an XML file they are using in the scripts that calls for changes to be made based on the variant requested by the game. Attached here is an image of the XML file that is calling for the 315p and 325a.
This comes with a nasty side effect for us working in the CryEngine SDK at the moment, and that is we really have no real way to get these variants working for cinematic sequences. CIG has we all know heavily edited CryEngine and this includes adding custom classes and other code to get spaceships working. They use a Vehicle entity for in game stuff but when we do cinematics we need to use a Physics/AnimObject entity for track view animations. The issue for us is that we do not have a way to call on these modifications as we would if we were using a vehicle entity.
Here are a few images showing the best I could come up with after ******** around for an hour or so. I used the character editor and attached the 325a “body kit” to the base 300i and saved it out as a .cdf to call back into the editor as an AnimObject to use in a sequence. I originally planed to showcase the 325a in a video I was going to make this weekend now that it’s available in arena commander.
Besides the layering issue there is also a hard set issue on the 325a’s bodykit not animating which totally ruins it for fan-made sequences. The same goes for the Aurora variants and it's starting to show up with the Hornet as well and is assumed to follow suit with anything else in the pipeline.
This isn’t a write up with a solution, sorry. I just wanted to make it known out there for fellow modders/video makes that Variants are FUBAR’d ATM and I don’t see it getting better until we get an official Star Citizen SDK. I will keep trying to see if I can’t get things to work properly but I wouldn’t hold my breath. I only have about a month’s worth experience playing with the SDK and I am still learning a lot. If anyone here knows more than I, (a devs input would be AMAZING) and has any input on this issue feel free to share your thoughts and ideas.
PS: If you guys don’t see any videos from me for a while, this is why just as a heads up! ;)
