Using a translation layer was the best decision...why ?
They are making a translation layer as universal as it can get for their engine....because it will be universal for their engine, it will make extremely simple and fast to convert other Source engine titles to LINUX.
This gives another benefit that is reduce the porting costs to very low levels....making it even easier to achieve profits from Linux ports....one aspect that was discussed here at Phoronix ad nausea.
No matter they are using a translation layer, they are achieving an impressive performance....and they said that they can squeeze easily 5 % more of speed from further optimization of that layer.
Even if this only at 1st glance applying to Source Engine, the teachings they got and the tools they learned to use to do it, might well apply to other engines like UE3 or others....this is where their assistance to other partners using other engines can be useful .
They are making a translation layer as universal as it can get for their engine....because it will be universal for their engine, it will make extremely simple and fast to convert other Source engine titles to LINUX.
This gives another benefit that is reduce the porting costs to very low levels....making it even easier to achieve profits from Linux ports....one aspect that was discussed here at Phoronix ad nausea.
No matter they are using a translation layer, they are achieving an impressive performance....and they said that they can squeeze easily 5 % more of speed from further optimization of that layer.
Even if this only at 1st glance applying to Source Engine, the teachings they got and the tools they learned to use to do it, might well apply to other engines like UE3 or others....this is where their assistance to other partners using other engines can be useful .
Comment