[Lightspeed]

Probably. Also, would reducing the texture file sizes lead to a performance improvement, or are thy stored decompressed on the GFX card memory anyway?

[Taristin]

Now that I have no idea about... I'm using the extent of my hardware knowledge with that last post I made...

But it'd probably help to have smaller sized, or resolution files, as long as you don't kill the detail.

[Lightspeed]

I asked because that might be my performance drain; I have all those neat 32bit TGA files.... (>100 MB) Would it help to convert them to jpg (<20 MB) or wouldnt it make any difference because the graphics card stores the textures in an uncompressed way anyway (>100 MB again) ?

Wheres the coders when you need them

[xenobyte6666]

in hl&t in d3d the main bug that casued it to be unplayable was that the direction of fire of the guns stayed in the same direction all the time, when i moved the mouse to aim elsewhere the guns stay aimed in the one direction...
weird bug...

[xenobyte6666]

ah got rid of that bug soz, tried diff setting and it worked right...

[xenobyte6666]

in d3d hl&t mode 1024x768 32bit -t32 -cell and vsync off the fps i got didnt go below 40, most stayed around 70-100.

i have 2500xp barton, nforce2 mobo, 1gb ddr400, geforce4 ti4200 128mb.

btw i think the bug i described relating to hl&t before was in opengl.....

the only probs i can see with it in d3d, are :

the targeting window in bottom left corner of screen, dont look right, not detailed enough, all u see is shape of ship no detailed textures....

in briefing - ship selection bit, the window where it shows u the ship selected, only shows a small part of the ship - and is very pixellated - looks like it just need to be zoomed out lots and lots.

hope this info is useful...

[Lightspeed]

do you use all my 32bit stuff?

Also, why do you use cell shading? O.o

On latest builds i get 70 FPS when theres not much happening (i'm v_synced to 70), 56 FPS when theres only minor stuff, 15-35 FPS when theres lots of action.

I used to get steady 70 FPS on HT&L, so something must really drain LOTS of performance.

i-p4 2.4 GHz (800 MHz FSB)
Radeon 9800 128 MB
512 MB RAM (DDR400, dual channeled)
Asus P4C800 Deluxe Mainboard

[Taristin]

Bugger, if I'm staring at blank space I get 35 fps. If I'm moving through empty space I get 30, and if I'm looking at one decent sized capship, I'm lucky to get about 24fps...  It's usually at about 6... And this is in standard mode. 32bit kills my PC.

[Solatar]

Something in the newer builds is even making the cursor move "slow" in the menus. And I have an ATI Radeon 9000 Pro 128mb, gig of DDRAM, and a 1.8GHz P4. What is it that's slowing everything down so much?

[Lightspeed]

thats why i need that -lines thing... Anyone know the command line? Or even better, anyone knows what the problem is / could be?

Older builds were heaps faster! (especially the buggy HT&L builds -- my FPS NEVER dropped below 70)

[Solatar]

Exactly.

I thought the -lines thingy was like in a special build or something.

[Lightspeed]

no, they said it's implemented in all newer builds

[Taristin]

Try it in debug builds?

[Lightspeed]

doesnt work either. Ive done some tests. Starting a new thread

[CP5670]

Ah, this has some of those new planets; excellent.

By the way, those "hi resolution" background nebulas are still in there and probably should be removed, since they look much worse than the standard ones ingame (this has been documented before). I rebuilt the VP without those and it also turns out to cut the size of the file by over half.

Something in the newer builds is even making the cursor move "slow" in the menus. And I have an ATI Radeon 9000 Pro 128mb, gig of DDRAM, and a 1.8GHz P4. What is it that's slowing everything down so much?

This is something I noticed with all of the builds since 3.55, but it does seem to have gotten worse with the 11_18_2003 one.

[Lightspeed]

huh? which nebulas that look worse?

[Triple Ace]

Originally posted by Lightspeed
ht&l isnt THAT buggy anymore... It's playable.

Although theres been massive slowdown on the latest builds. Even HT&L is not really "ubar-fast" anymore. I tried to find out what exactly causes the slowdown, but i didnt manage to find out what the heck the lines commandline was (2 people have posted one, but neither of both works)...

HT&L is very buggy. How do you explain the crashing to windows with no error message?

[Lightspeed]

... which does not happen on my machine

[CP5670]

It happens to me every now and then, but no more so than in the last few builds since 3.55. Same symptoms as that good old targeting crash.

huh? which nebulas that look worse?

well, all of them. This was talked about in another thread about a month ago; the excessive blur in them nullifies any effect that increasing the size gives and makes them actually look worse ingame. I would post a screenshot showing the difference but for some reason I can't get a proper IP address, which prevents me from connecting to any FTP servers to upload the images.

It might actually be worth redoing these nebula images from scratch (as is being done with the planets), as they are relatively easy to make.

[Lightspeed]

actually youre the first (and only) one who says that

someone post some screenshots of scaled nebulae (new & old) and youll see what I mean. They're better. at the same size, they do not have any visible blur.