Quore 0.3 is out

[Dreadlorde]

Right now I'm working on cleaning up the code. Tabs are just four spaces, and a bunch of other things that make it hard to read. Also, is there planned support for windows? Because I also started to remove windows specific stuff; directsound, windows gl, et cetera. Is that alright? If not I can just start over, I haven't done much.

p.s.
Did you get the PM I sent you?

[lxndr]

Right now I'm working on cleaning up the code. Tabs are just four spaces, and a bunch of other things that make it hard to read. Also, is there planned support for windows? Because I also started to remove windows specific stuff; directsound, windows gl, et cetera. Is that alright? If not I can just start over, I haven't done much.

p.s.
Did you get the PM I sent you?

I'm using indent to format the code. It was fine for me, I've got a 1680x1050 display, so very long line were not a problem for example, but this can be a problem for others, Nontheless, it would be nice to keep the code consistent and let indent or another code formatter do the job.

Here is the command line I use:

alias indev='indent -br -brf -ce -l150 -lc150'
alias indent='indent -nbad -nbap -nbbb -bbo -nbc -nbfda -brs -c40 -cd40 -ncdb -ncdw -ci4 -cli4 -cp40 -cs -d0 -di14 -nfc1 -nfca -ip0 -nhnl -i4 -lp -pcs -ppi2 -nprs -npsl -sc -sob -nss -nut'

astyle is a bit more user friendly :-)

Windows support is planned, not in the short term, I would like Quore to run on x64 first, but if one day, me or someone else want add support for it, it should be ideally a matter of configuring VC++ without putting his hands into the code.

Ps:
Got it.

[Dreadlorde]

I'm using indent to format the code. It was fine for me, I've got a 1680x1050 display, so very long line were not a problem for example, but this can be a problem for others, Nontheless, it would be nice to keep the code consistent and let indent or another code formatter do the job.

Here is the command line I use:

alias indev='indent -br -brf -ce -l150 -lc150'
alias indent='indent -nbad -nbap -nbbb -bbo -nbc -nbfda -brs -c40 -cd40 -ncdb -ncdw -ci4 -cli4 -cp40 -cs -d0 -di14 -nfc1 -nfca -ip0 -nhnl -i4 -lp -pcs -ppi2 -nprs -npsl -sc -sob -nss -nut'

astyle is a bit more user friendly :-)

I'm using vim editing, I have set to use the actual tab character and my tabstop is set to 4.

Windows support is planned, not in the short term, I would like Quore to run on x64 first, but if one day, me or someone else want add support for it, it should be ideally a matter of configuring VC++ without putting his hands into the code.

Damn it, I just finished removing all of the horrible #if/n/defs relating to win32 from my tree at github.

Ps:
Got it.

Got it.

[lxndr]

I'm using vim editing, I have set to use the actual tab character and my tabstop is set to 4.

From the doc

Note: Setting 'tabstop' to any other value than 8 can make your file
appear wrong in many places (e.g., when printing it).

Go for tabs, with the default tabstop, if someone else comes and use a different editor, we would have to switch back to space characters.

Damn it, I just finished removing all of the horrible #if/n/defs relating to win32 from my tree at github.

More than once I wished to drop them, maybe some of them are useless, For example I think that the D_BeginDirectRect and D_EndDirectRect functions are for DirectX, not sure about that, but if it's the case, we could remove a bunch of useless code.

[Dreadlorde]

So. What do you want quore to be? I've been looking at features from other quake engines to see what I find useful.

p.s.
when are you on jabber the most? I'm on most weekdays all day (I may not be there, but I'll get your message). I'm on Eastern Standard Time (-4).

[MH]

From the doc

Go for tabs, with the default tabstop, if someone else comes and use a different editor, we would have to switch back to space characters.

More than once I wished to drop them, maybe some of them are useless, For example I think that the D_BeginDirectRect and D_EndDirectRect functions are for DirectX, not sure about that, but if it's the case, we could remove a bunch of useless code.

The 8 vs 4 thing is only a problem if the original author was inconsistent in their use of spaces or (real) tabs. As it happens, ID were inconsistent, and in cases where spaces were used instead they used 4. So in this case setting to 8 will actually make it look wrong, unless you run it through a formatter first (in which case both sides of the problem go away).

[lxndr]

So. What do you want quore to be? I've been looking at features from other quake engines to see what I find useful.

p.s.
when are you on jabber the most? I'm on most weekdays all day (I may not be there, but I'll get your message). I'm on Eastern Standard Time (-4).

Hi Dreadlorde ! Sorry, I've been quite active these days at fixing stuff I made, which left no much time for anything else. Now the biggest part is behind me, I still need to clean up few things but a release should hopefully come for next week and I'll have much more free time too.

I'm not currently planning to add extra stuff for now, there's some rendering artifacts I would like to be fixed and it's a very long process. But if you're up to add new stuff, that's great !

I've read the thread about adding support for Q2 models, I like the idea of making life of modders easier but I'm wondering if they would not prefer working with Q3 models, which is already supported in many engines including JoeQuake which Quore is based on.

Anyway, I think it's the way to go, engines should not rely on file format that no one knows, pak, wad, lmp, mdl. We need to support standards that mappers, skinners, modders are used to, or at least support file format that common tools can recognize.

new PM to come :-)

[Dreadlorde]

Hi Dreadlorde ! Sorry, I've been quite active these days at fixing stuff I made, which left no much time for anything else. Now the biggest part is behind me, I still need to clean up few things but a release should hopefully come for next week and I'll have much more free time too.

That's fine, whatever you have in real life coes before the game (supposedly ;D).

I'm not currently planning to add extra stuff for now, there's some rendering artifacts I would like to be fixed and it's a very long process. But if you're up to add new stuff, that's great !

I've been working on some little things here and there, nothing really special. But I understand wanting to fix isses that are already there before adding more features. I think that's what I'm going to do.

I've read the thread about adding support for Q2 models, I like the idea of making life of modders easier but I'm wondering if they would not prefer working with Q3 models, which is already supported in many engines including JoeQuake which Quore is based on.

If it can be added easily and without mucking things up, I don't see why there couldn't be support for Q3 models too. You're the lead in quore, so you can do whatever you want.

Anyway, I think it's the way to go, engines should not rely on file format that no one knows, pak, wad, lmp, mdl. We need to support standards that mappers, skinners, modders are used to, or at least support file format that common tools can recognize.

That's how I feel too.

new PM to come :-)

Got it.

[Baker]

That's fine, whatever you have in real life coes before the game (supposedly ;D).
I've been working on some little things here and there, nothing really special. But I understand wanting to fix isses that are already there before adding more features. I think that's what I'm going to do.
If it can be added easily and without mucking things up, I don't see why there couldn't be support for Q3 models too. You're the lead in quore, so you can do whatever you want.
That's how I feel too.

Got it.

I like Q3 models. It would be nice if Q1 engines supported them.

Isn't there an issue with lighting them due to the number of triangles or something to that affect in Quake 1 with the way that Q1 does lighting?

I'm not saying I am correct. This is my understanding.

[lxndr]

I like Q3 models. It would be nice if Q1 engines supported them.

Isn't there an issue with lighting them due to the number of triangles or something to that affect in Quake 1 with the way that Q1 does lighting?

I'm not saying I am correct. This is my understanding.

You must be right. JoeQuake had a lot of things related to Q3 but I guess it's only a partial support.

[Dreadlorde]

lxndr: I noticed today that there's already some code for Q3 models in gl_models.c. Did you start on this a while ago?

[lxndr]

That's fine, whatever you have in real life coes before the game (supposedly ;D).

Supposedly, last week, it was only coding at work and coding at home. I think I need a break ;D

[Dreadlorde]

Supposedly, last week, it was only coding at work and coding at home. I think I need a break ;D

Did you get my email and PM? You also need to get on jabber more.

[petermg]

need help installing/configuring

Can you please help me? I am having problems when I rung ./configure in Ubuntu 9.10. Here is the error I'm running into:

configure: error: missing xf86dga library


any help would be greatly appreciated. I looked in synaptic for "xf86dga" and installed the only thing that came up but that did not fix it

[Dreadlorde]

What graphics card are you using? Can you utilize OpenGL? If you can, you probably don't need the x11proto-xf86dga-dev package (that's the one you installed, right? It's the only one I found looking on packages.ubuntu.org).

./configure --disable-dga --disable-vmode --disable-misc --disable-dbus --disable-mp3