 | | Re: Some bugs with LDGLite
|
|
(...) I'm pretty sure that's a bug with the OS X version of GLUT. I bet it gives 2 events for each key or button press. Probably a key up and a key down event. I'll have to filter out the extra ones. (...) Hmmm, a quick calculation says 1024x768 (...) (24 years ago, 10-Jun-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Could someone run a perspective mode test on ldglite?
|
|
(...) Hi Jim, the internet is a bit smaller than you thought, eh? Imagine my surprise to find a website full of pictures from someone (besides myself) who actually uses ldglite? (...) I must've missed that elsewhere part of the thread. Oh well, I'll (...) (24 years ago, 10-Jun-02, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: Could someone run a perspective mode test on ldglite?
|
|
(...) Hello, all! My name is Jim and it just so happens that the web site you've been discussing in regards to the rendering problems is mine. I'm new to LUGNET, so imagine my surprise when I first start reading its Mac section and see people (...) (24 years ago, 9-Jun-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Some bugs with LDGLite
|
|
(...) OK, this on made me laugh (the odd things that happened)j. First I didn't know that the enter key and space bar did anything, but they don't work quite right either. The spacebar causes LDGLite to draw two steps. The enter key causes LDGLite (...) (24 years ago, 7-Jun-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Some bugs with LDGLite
|
|
(...) Just to be clear, the two step jump has nothing to do with LDGLite Launcher. Well, the problem with the full screen modes for me is that the parts remain highlighted. I can't go any bigger than about 750x550 if I want the selected part (...) (24 years ago, 7-Jun-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Could someone run a perspective mode test on ldglite?
|
|
(...) Hmm. I was under the (mistaken) impression that glPolygonOffset was introduced in OpenGL 1.2. A NULL return from wglGetProcAddress means that the extension function requested doesn't exist. Apparently the ATI driver returns NULL for core (...) (24 years ago, 7-Jun-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Some bugs with LDGLite
|
|
(...) That's most likely a problem with the version of GLUT available for Mac OS X. It's known to have bugs like that. There's an improved version of GLUT available, that I might try to use for the next release, but I don't know how difficult it is (...) (24 years ago, 7-Jun-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Some bugs with LDGLite
|
|
(...) Hehehe. I know. I never did implement it. I think I tried to disable it (so that I didn't have to delete it from the layout), but I couldn't figure out how. OK, so I didn't put that much time into it. That is why the version is pre 1.0. :-P (...) (24 years ago, 7-Jun-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Could someone run a perspective mode test on ldglite?
|
|
(...) I knew it! The opengl driver for my older Rage Pro is terrible. I think they just tested it for quake, which probably doesn't use lines at all. (...) I'm not sure what that NULL means. Does it mean there's no fn, or that it falls back to a (...) (24 years ago, 7-Jun-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Could someone run a perspective mode test on ldglite?
|
|
(...) True, but lucky for you, I was following this thread, and my work machine (Windows 2000) has a Rage 128 Pro. I get the same effect with the -J option. The -z100 -Z2000 fixes it. One really strange thing, though. As far as I can tell, LDView (...) (24 years ago, 6-Jun-02, to lugnet.cad.dev.mac)
|
