Quote: "When did word or photoshop or any of your other software present you with problems like fpsc?"
Windows?
Almost every day.
Seriously.

Damn you, Bill Gates!
Quote: "Unreal are giving away their engine for $99 so dont say we have to put up with all the nonsense because of the cheap price."
(Actually, $99
+ 25% royalties after the first yada yada yada; not at all a bad deal though.). Anyway, the conviently and
always overlooked factor with the tired old UDK vs FPSC debate is that
you actually have to know how to program in order to get somewhere with UDK. With FPS Creator; not so much. It's the same thing as; "
Oh, well, 3DSMax is better than Milkshape, so I'll just "buy" (yeah, we'll call it buy) Max!" If you don't know how to model, and you don't have any
incentive to learn, then it's not really going to make a difference which program you use.
Another analogy for UDK and FPSC (because I enjoy coming up with them

), is going to a car dealership, and there you see two cars. One car is an automatic [FPSC]; a Honda, and it costs $10,000.00. The other car, has a manual transmission; a Corvette [UDK], and it costs $12,000 (just a little bit more).
But, you don't know how to drive a stick, nor do you have a lot of experience with a rear-wheel drive sports car on winter roads. Both cars can get you where you need to go, but the Corvette has a better engine (<flawless anology ftw!).
So, you can either, stick with FPS Creator (I mean; the Honda), and leave the dealership right then and there and start your trip. Or, you can take the extra time to learn what you need to learn to get somewhere with the Corvette. The problem is; most people don't have that incentive to learn what they need to to drive the Vette, which is why I consider most of these UDK vs FPSC debates completely irrelvant. 99% of the time at the end of the day, our FPS Creator developer, and our UDK developer, both have nothing to show for. And most of the time, it's our own aggrevated FPS Creator developer that stands behinds UDK, unaware, or only partially aware of the difference in work load between the two.
Now if you
doknow how to work with UDK
and how to write your engine for it, then first, I would like to ask why you are still worrying about FPS Creator in the first place?

Secondly, I would like to ask when your UDK game will be finished so I can play it. Finally, you still need to keep in mind that FPS Creator was not intended to rival UDK. It has it's problems (as any software does); but they can all be overcome with time and effort.
EDIT: A little off-topic mayhaps; but I was only killing time until my car gets back.
Kravenwolf