Home › Forums › FxGen Development › Bugs

Current state of FxGen

Mon, 02/04/2008 - 20:51 — Dentoid

Hey
I haven't messed with FxGen in quite some time, but I just got back to it since we might use it at work. However, I noticed now that there's this big ProTex branch that I haven't seen before. (I know the story about protex, I've just somehow missed that the code has actually been thrown into the SVN repo.)

So... Now I'm curious, what's supposed to be used really? Is the protex changes additions on top of the core FxGen, or is it more separate? Are they supposed to be compatible? The reason I'm wondering is that I kinda don't want to do a lot of content using something that will eventually turn obsolete, or change a lot. So... What are the plans there? :)

‹ Fxgen_v0_5a - editor doesn't even start Issue with project ›
Fri, 02/08/2008 - 06:07 — pencechp

Wondering the same thing

I messed around with the FxGen editor some a while back, and had left because of the lack of platform independence. Now with the Linux compilation up and running, I'd love to use FxGen in my latest project -- what's the real status?

Fri, 02/08/2008 - 10:38 — qduaty

The Protex branch consists

The Protex branch consists of Cyber_wiz's contributions to FxGen that use libnoise (Perlin noise library) to generate patterns. It's rather difficult in use. I used that directory to complete my linux port, without messing the main branch. The port is ready and there is a binary libfxgen with a test program in protex/LinuxBin. Beware that they are 64-bit AMD and won't work on an x86 environment. My next patch (which will make the main branch linux-compatible), will be available in a few days.

Besides, I am experimenting with a new editor framework, based on GTKMM.