Search the web
Sign In
New User? Sign Up
quark-python · QuArK Python Tech Info
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Show off your group to the world. Share a photo of your group with us.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
QuArK major 3D view issue   Message List  
Reply | Forward Message #6957 of 6984 |
This is my responce to a posting made on the quark board.

--- In quark@yahoogroups.com, "rd" <realdespair@y...> wrote:
> Is there any way to see the models in the editors 3d views?
> Its quite difficult to place them now.

I can certainly understand that, but for H-L2, unfortunately no and
probably never will since two of the experts specializing in H-L2
decided to leave the QuArK project. 8-(

> Another problem im having is the sluggish update of the 3d views
when
> editing. My map isnt that big and isnt using any negative polies
(which
> ive noticed makes it even more sluggish). The map is medium sized
(ive
> made bigger and complexer for hl1 and it had no effect on quakrs
> performance) and every time i move something the 3d view takes 4-5
> seconds to update, which makes editing with a (textured) 3d view
open
a
> bit impossible. I guess it has to do with steam?

I am not to sure it does have to do with steam at all. I have also
noticed this problem lately but even older versions of QuArK have
always had issues with the 3D views locking up and smearing.

What I have recently recognized, is that there is no problem if the 3D
views are not used at all, which is a real bummer, and that, unlike
before, I keep getting this "progress bar" saying it is "preparing
faces" which I never got before but the editor would still "lock up"
for 3 to 5 seconds so I suspect that the same process was taking place
but just didn't show the progress bar.

It acts like the editor is going through an "exporting" process to
update and renew the 3D view(s) anytime something is touched in any
other view or the structure tree, which is a real pain in the Axx and
definitely discourages making any kind of decent size maps using
QuArK.

I have been harping about this for years now, but with older games
that
are very limited in their size and complexity, I don't think the
problem has been all that apparent until now with greater demands
being
required of QuArK by the newer games.

Personally I think how QuArK works with any 3D structure needs to be
looked into and revamped all together, which is probably a horrendous
project, but one that really should take the up most priority and
attention by all involved in its development, including me! But being
totally inexperienced in 3D programming, I am at a big disadvantage in
trying to do anything about it on my own. 8-(

So the best I can do right now is pass this posting on to the quark-
python board and hope others will help take this issue on and try to
recruit others that do have the education and experience in the 3D,
OpenGL or other compatible areas.

Thank you for confirming my long felt suspicions.
Best regards,

cdunde






Sat Sep 17, 2005 7:49 pm

cdunde
Offline Offline
Send Email Send Email

Forward
Message #6957 of 6984 |
Expand Messages Author Sort by Date

This is my responce to a posting made on the quark board. ... I can certainly understand that, but for H-L2, unfortunately no and probably never will since two...
cdunde
Offline Send Email
Sep 17, 2005
7:49 pm
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help