Maybe instead of posting a link to a zip file on a webserver on a 14.4k in the middle of Bumfuck, Nowhere, you could simply state what the problem is.
Roma Loom at
I can send it to ya via e-mail... if You don't mind...
TX at
Why don't you just SAY what the bug IS? If it's the HOM on the menu, it's known about. I told JonoF a quick method to fix it before release, but I guess he didn't feel like including it.
Mblackwell at
TX said
Maybe instead of posting a link to a zip file on a webserver on a 14.4k in the middle of Bumfuck, Nowhere, you could simply state what the problem is.
I laff
And yes, fine, post a zip, but please state your problem since we might not even need to look at the damned zip :P.
Roma Loom at
The thing is that I don't have the bugs described in this videoclip except for the HOM in the menu. The other thing... well I was already sending this file to You while posting... :?
mean_person at
fu#king narod.ru. Please tell the address of a good free hosting.
I too badly know English language what to explain that it for a bug, simply look this clip
clip
Awesoken at
From your video, I can see that you have most of the standard high-res textures as well as your own modifications. I don't recognize your spinning icon. I suspect there are some problems in your DUKE3D.DEF. Do you get any errors in your console log? Would you mind posting your DUKE3D.DEF?
mean_person at
Awesoken said
From your video, I can see that you have most of the standard high-res textures as well as your own modifications. I don't recognize your spinning icon. I suspect there are some problems in your DUKE3D.DEF. Do you get any errors in your console log? Would you mind posting your DUKE3D.DEF?
Looking at that clip is very interesting and although I cannot help you I want to bring up a problem I'm having and maybe it will ring a bell somewhere in Kens mind regarding both our problems.
My PC is an Intel 2.8 gig Northbridge with a GeForce ti 4200 128 meg graphics card.
My wifes PC is a Intel 2.8 gig Prescott with a 96 meg Intel 82865G OpenGL graphics controller.
With this latest build she gets very similar problems to what mean_person is getting wheras I dont have any problem at all.
Let me explain in more detail.
Jonothan added the following code to display the current map being played.
if (savehead.volnum == 0 && savehead.levnum == 7)
gametext(160,180,savehead.boardfn,0,2+8+16);
The second line is the line of interest.
With the build as it stands, like I say she gets very similar problems as mean_person, not as bad, but also the mapname NEVER appears in her Save or Load menu's ever, whereas on my PC it works great.
This is the interesting part:
I changed the code as follows and recompiled.
if (savehead.volnum == 0 && savehead.levnum == 7)
gametext(160,180,boardfilename,0,2+8+16);
This now works 100% on her PC and that HOM effect is completely gone.
BUT...
On my PC, the Mapname is now gone and although I dont get any HOM effect, when I play a user map, and die and it says "Load last game: Y/N" and if I press "N" it says "Starting Hollywood Holocast" and that map starts instead of the usermap I was playing.
I know this sounds crazy and you are saying "what the hell has one to do with the other" but its happening so she has reverted back to the previous release which may be the best thing to do for anyone not interested in multiplay.
It brings me to the conclusion that we need beta testers all with different graphics cards.
I am still looking into it but am finding the new release very unstable as far as changing the code etc, whereas the previous release was rock solid and you could do whatever you liked.
The other interesting thing is although my wife has a more powerfull PC than mine, there is no way in hell she can play with 16 or 32 bit Poloymost as every now and then her PC locks ups solid and she has to wait about 30 seconds or so for it to unclock itself.
This happens even with her Duke3d.def file removed so no new textures are being used.
On my PC I have no problems at all and use even higher resolution textures than the Parkar pack.
mean_person at
When I am switched to a classical render mode, I see the same effect in the menu. :(
TX at
ProAsm said
The other interesting thing is although my wife has a more powerfull PC than mine, there is no way in hell she can play with 16 or 32 bit Poloymost as every now and then her PC locks ups solid and she has to wait about 30 seconds or so for it to unclock itself.
This happens even with her Duke3d.def file removed so no new textures are being used.
On my PC I have no problems at all and use even higher resolution textures than the Parkar pack.
Huh? You have a faster/cooler running processor (2.8 Northwood vs 2.8 Prescott, Northwood is superior) and a better video card. Your PC is better than hers is. Locking up for 30 seconds at a time sounds like an effect of possible thermal throttling.
ProAsm at
Firstly there is no way a Northwood is faster than a Prescott.
My PC is 18 months old already where hers is 2 months only.
Northwood only has 512k L4 cache where the Prescott has 1 meg.
I do agree however that my graphics card is superior.
Locking up for 30 seconds at a time sounds like an effect of possible thermal throttling
Yes I also though that but in all other games and MS Office packages etc it works 100%, no lockup nothing.
Only in Duke3d does it do this and you can see it when you play a map and suddenly walk or run into a wide open space with lotsa stuff all over the place, it just locks solid and after about 30 seconds you see it start jerking a bit then come right and you can carry on playing.
TX at
ProAsm said
Firstly there is no way a Northwood is faster than a Prescott.
My PC is 18 months old already where hers is 2 months only.
Northwood only has 512k L4 cache where the Prescott has 1 meg.
That doesn't matter. The Prescott is not faster than the Northwood. Bench any Prescott against a Northwood of the same speed (in something that isn't extremely cache sensitive, anyways) and the Northwood will win. The Northwood would win for sure if they both had the same amount of cache.
Though all I could immediately find was a shitty THG benchmark, here's an interesting passage from it:
At the beginning of the tests for this project, we had a hunch that the resulting curves of the P4 Prescott and those of the Northwood processor would cross in several benchmarks. This was based on the assumption that Prescott, thanks to the double cache size and the 31-part pipelines, could produce more performance at a higher speed than the Northwood processor.
From this perspective, the results are sobering, because even at 4 GHz little changes in the balance of power between the two cores. Northwood is and remains the faster processor in common applications, even if the difference can be virtually ignored in application.
So, returning to what I said.. you have a better processor, as it runs faster and cooler than what your wife has. :p
ProAsm at
Hi TX, thanks for that info and yes it looks like you are right although her PC will load a large pic faster than mine but maybe thats the extra cache as we both have 1 gig memory.
I must admit the Northwood runs quieter, cooler and seems more stable.
It makes me wonder why Intel have chosen to model their 64 bit CPU around the Prescott.