[MatthTheGeek]

I need to find a shorter name for that, it's quite a mouthful.

So yes, this is mostly, for now a barebone proof-of-concept of import and conversion of Star Citizen ships into FSO.

Featuring for now, the P52 Merlin, with placeholder stats and weapons, and a single dogfight mission with waves of two enemy fighters against you.

Download v0.2a Standalone (Mediafire)



This uses the MVPs for now (2014 beta, but should probably work on .12 as well), but should eventually become standalone. This is now standalone. Yayifications!

Any feedback on what I have so far is welcome.

EDIT: rorry, clicked on the wrong subforum. Thanks to E for fixin'

Link to the release thread on the SC forums

[Lykurgos88]

This is awesome! Downloading now. 

Chris has to try hard if he's gonna beat the FSO space combat gameplay.

[Nyctaeus]

Alrough the design is pretty cool and extremly well-detailed, I'm wondering if we can found any usage for this. This is somekind of a fighter, and for today standards in FSO, 20-30k polys for a fighter/bomber is pretty high. What's with 172k? If this thing would even be useful, it requires some serious optymalization or at least LODs. Despite that, cool stuff from Star Citizen is always welcome .

[MetalDestroyer]

What, where is the Hornet ? the Freelancer, the Aurora ? :ninja:

[MatthTheGeek]

[MatthTheGeek]

The v0.2 Standalone is now released. If possible, I'd like to have basic functionality feedback on this before officially releasing it in the SC forums

This ships with a shadow/defered exe, but should work with any recent nightly.

EDIT: for info, a fatal bug related to sound tables will be fixed in the next release. If you encounter a CTD after a couple minutes of gameplay, that's the one. Sorry! Official release should be this evening or tomorrow. My thanks to Kobrar for his testing.

[coffeesoft]

Nice ship, and nice colors 

[Shivan Hunter]

So I tried this earlier today (**** Mediafire). Very fun, and excellent job converting the model to FS!

The only technical issue I see is that it gets a bit laggy with several ships on screen. That's no surprise given the number of polies on the Merlin, but I noticed it had no LODs. (I might be able to check that out sometime, since I have free time now and Blender is awesome)

About the gameplay (I know it's just POC now) - how much is actually known about SC ships/weapons? Will it be easy to translate what they have into numbers for FS?

Excellent work! the SC fans will probably be nerdgasming over this.

[MatthTheGeek]

That's no surprise given the number of polies on the Merlin, but I noticed it had no LODs.

More or less waiting on CIG to do them for me (Hornet will get LODs for the DFM).

About the gameplay (I know it's just POC now) - how much is actually known about SC ships/weapons? Will it be easy to translate what they have into numbers for FS?

We know little and everything we know right now is subject to change. There are things that we definitely won't be able to emulate with FSO as it is (destroyable manoeuvring thrusters, for example) and some that will require some heavy trickery if we want to emulate them (shield penetration depending on shield thickness vs ammo used), but nothing stroke me as extremely problematic so far.

I'll try to make it very clear in the release post SC-side that this won't be able to replicate perfectly SC gameplay nor is it trying to.

[MetalDestroyer]

Damn, if Gran Turismo 6 wasn't there; I would gladly take a look.

[MatthTheGeek]

Link has been updated to v0.2a. Released on the SC forums (see bottom of first post).

[MatthTheGeek]

Sneaky WIP



Original for comparison


Need to figure out why colour mapping is off.

[pecenipicek]

invert the mask?

[MatthTheGeek]

Ok I found it and it's pretty heavy ****.

They use vertex color to tint particular tilemapped areas of meshes.

The Aurora normally:


Now with vertex color disabled on a particular material:


Disregarding the fact that neither FSO's graphic code nor the pof format support vertex coloring (or at least not on textured objects, cf jump nodes) (source: The E), it seems that neither obj nor fbx export from the CryEngine Sandbox preserve vertex colors to begin with (obj doesn't even support it), which means I can't even manually/scriptically sort vertexes by colors and assign them different textures to match the color scheme.

I'm gonna investigate other ways to convert cgf/cga from CryEngine, but I doubt they won't have the same problem. It looks like I'm pretty screwed on that front.

I'm open to ideas.

I swear, tilemapping will be the death of me

[Kobrar44]

The only two ways I see are to either use one tile per one color or to give this thing proper uv-mapping. I can take care of either.

[MatthTheGeek]

The "one tile per color" solution is what I meant when I talked about

manually/scriptically sort vertexes by colors and assign them different textures to match the color scheme.

which I can't do since color isn't even exported, which means the info on where the color is is lost in conversion. I would have to guess based on what I see in the sandbox and manually reassign each face to a different material, which would be even more time-consuming and error-prone, not to mention it would require me to learn how to modelling software, which I'm actively trying to avoid for my sanity's sake.

[MatthTheGeek]

Welp, given up on colors.



On to engine and weapons now.