Japanese

https://translate.google.com

PFXファイルはParticleFXのシミュレーション結果を保存するファイルフォーマットです。
このファイルはバイナリ-ファイルであり、バイトオーダはBig Endian(Motorola形式)です。

translated to:

PFX file is the file format in which to save the simulation results of ParticleFX.
This file is binary - is a file, byte order is Big Endian (Motorola format).

Just copy & paste sections as it won't do the table as is.
 
LOL, I know what it is :) that's why I need the translation of what's in the table.
Anyone wrote a pfx parser?

https://translate.google.com

PFXファイルはParticleFXのシミュレーション結果を保存するファイルフォーマットです。
このファイルはバイナリ-ファイルであり、バイトオーダはBig Endian(Motorola形式)です。

translated to:

PFX file is the file format in which to save the simulation results of ParticleFX.
This file is binary - is a file, byte order is Big Endian (Motorola format).

Just copy & paste sections as it won't do the table as is.
 
More questions:

It seems that pfx is an IFF format, so it has a few limitations, and so it's probably big endian encoded.
Swapping will introduce an overhead that I don't want.

Does anybody know of a format similar to IFF, but little endian encoded?

creacon
 
Hi
You can use google translator. If you want to translate this part properly I can give it to my friend who is working in Japan, so send me a private message if you still need it.
 
Swapping will introduce an overhead that I don't want.

You must be kidding...
What kind of "overhead" is introducing code:
unsigned int src = 0x12345678;
unsigned int dst = ( ( src >> 24 ) & 0xFF ) | ( ( src >> 8) & 0xFF00 ) | ( ( src << 8 ) && 0xFF0000 ) | ( ( src << 24 ) & 0xFF000000 );

Bit-shifting and bit-wise and operators are any CPU native instructions (and one of the easiest to implement in hardware).

Overhead introduced by any text-based file format is hundred times bigger..
 
Even if it is fast, it's still overhead.
Who says I am using or planning to use a text base format?
Anyway, this problem has been solved a long time ago.

creacon
 
Back
Top Bottom