QuArK Editor, anyone?

[Dario D.]

Has anyone used the QuArK Editor in place of Hammer?

What do you think of it vs. Hammer?

(QuArK = Quake Army Knife)

I'm trying to get accustomed to it to see if I'll be using it in place of Hammer.

So far it seems immensely more powerful, but immensely slower to build with.

 

[Dario D.]

It really isn't popular around here... :dozey:

 

[Angry Lawyer]

I never got along with Quark. No idea why, just felt...wrong. And that was back in the days of Quake 2.

-Angry Lawyer

 

[A.I.]

QuArK was my first editor in the days of Quake 2 too. Made some maps and stuff, but now I more got used to Hammer. But QuArK is still good to the newbies to mapping I think, yet it has to be mastered to make some things like in Hammer.

 

[Angry Lawyer]

Radiant was the tool to use. That, and Worldcraft. I started with Radiant when I mapped for Quake 2.

-Angry Lawyer

 

[Raeven0]

Tried Quark out of necessity. Hated it. With a passion.

It can't align textures at all, and the viewscreens were laggy and would turn into HOMs within two minutes

 

[Zeus]

I couldnt stand it, it was pretty bad

 

[Dario D.]

Tried Quark out of necessity. Hated it. With a passion.

It can't align textures at all, and the viewscreens were laggy and would turn into HOMs within two minutes

I've been having the same problems - except my viewports refresh and flicker like crazy whenever I click and move something, and yeah, I can't auto-align any textures or copy tex coords over to another face.

Advanced Prefabs, however, would probably be very easy to make with QuArK,... things that Hammer isn't so easy with, like curves.

I'm still trying to see if you can save prefabs...

 

[Hazar]

I've gotten used to hammer and see no reason to try this one

 

[cbxpm]

Has anyone used the QuArK Editor in place of Hammer?

What do you think of it vs. Hammer?

(QuArK = Quake Army Knife)

I'm trying to get accustomed to it to see if I'll be using it in place of Hammer.

So far it seems immensely more powerful, but immensely slower to build with.

Source Engine support in Quark is still under development. Important things are still missing, such as displacements and model rendering in 3D-View.

But all those features will come within the next mounths.

Anyway, Source is like a "flagship" for Quark. Many things are slower, and still need some improvements. It is programmed in Delphi / Python.

 

[Dario D.]

I opened one of my maps with QuArK, and it ran super slow. Apparently I'll need mega computer specs to run it any faster when working with a detailed map (my specs are AMD 2800+ and 6600 GT)

I couldn't even click on a brush or fly the camera without waiting a whole second for the editor to update the views.

...so I can't use it. Also my video card seems incompatible - the viewports flicker and refresh whenever I click on something or do anything, and it hurts my eyes.

Quark seems to need a little more time in developement before it's ready for my computer... :monkee:

 

[cbxpm]

I opened one of my maps with QuArK, and it ran super slow. Apparently I'll need mega computer specs to run it any faster when working with a detailed map (my specs are AMD 2800+ and 6600 GT)

I couldn't even click on a brush or fly the camera without waiting a whole second for the editor to update the views.

...so I can't use it. Also my video card seems incompatible - the viewports flicker and refresh whenever I click on something or do anything, and it hurts my eyes.

Quark seems to need a little more time in developement before it's ready for my computer... :monkee:

I am working with 6600 GT too, but have no problems with the views. There were some issues with an older nvidia driver, but now with the actual version it runs fine.

Yes indeed, speed is an important thing. We need improvements