tain.totalcodex.net

Posted: **Tue Mar 29, 2005 10:37 pm**

It seems to affect only WinMe and earlier. Win2k and XP machines are ok. We just need to identify what changed & I'm sure the fix will be straightforward.

Posted: **Tue Mar 29, 2005 11:46 pm**

I can help test a new build but my weeks are pretty busy so I'm not sure how much time I'd be able to put into it.

Posted: **Wed Mar 30, 2005 12:13 am**

If you need more people to test a new build just post here and I will check it out. I am having that Direct3D problem too and would like to get it fixed as soon as possible.

Posted: **Wed Mar 30, 2005 7:03 am**

Also if people could report if they had the same problem with the public beta that would be helpful too.

For the person with the Banshee card ->

A Banshee is a 3dfx card(unless someone else called their card a Banshee), in which case you should be able to use the 3dfx renderer.

Posted: **Wed Mar 30, 2005 7:12 am**

Folks: Try changing some of the prefs in the options area of the prefs screen, esp the CPU ones. The only thing I see changed between 255 and 257 that could cause an issue is that we force the screen prefs to reset the first time Build 257 or later is started up.

Posted: **Wed Mar 30, 2005 12:07 pm**

I did not have a problem with Direct3D in 1.5.1 beta. It worked perfect. Only after I downloaded and installed 1.5.1 final did I start to experience the low frame rate. I have also tried all different combinations of game settings including CPU settings and nothing has helped at all. Also, about the Banshee card I have, I was using 3DFx in game settings. They just called it BlasterControl. However, I quit using it because in Campaign it was causing all moveable players to flicker and in multiplayer it made the whole screen flicker. And even with the new graphics card put in Direct3D still didn't work and I still experienced the low frame rate.

Posted: **Wed Mar 30, 2005 12:43 pm**

No surprise here that ME is suffering the same problems as 98 (assuming 98 IS the common link), afterall, ME is more or less just a shiny windows 98, whereas 2k and XP are based on NT.

And while we're talking about ME, Baak, wth are you doing on that heinuous operating system?! That's got to be worst OS MS ever relased!

Posted: **Wed Mar 30, 2005 1:09 pm**

For folks who the public beta worked fine and now have low framerates using D3D try the below test build and post your results here.

1.5.1b Test

Edit: This build is fully interchangeable /w the regular 1.5.1 build.

Edited By CIK on 1112206683

Posted: **Wed Mar 30, 2005 2:07 pm**

And while we're talking about ME, Baak, wth are you doing on that heinuous operating system?! That's got to be worst OS MS ever relased!

I know, I know! The main reason I use it is because I couldn't get Myth to work on Win2kPro with Sygate Personal Firewall.

One time when I used to use it and had the firewall off I managed to get infected by a nasty worm that took me several days to clean up.

Interesting though, recently I played once and didn't realize I was still on Win2kPro and it seemed to work fine. I had set the Myth II ports open on the firewall for Myth and all was ok. So perhaps I'll try it again. Are there specific ports besides the 3453 that I should allow, or perhaps just allow Myth II open access in general? Any special settings I should know about? This is slightly off-thread for sure... Perhaps just email me at baak@orderofhpak.com

I only ever use WinMe to play Myth (and as a dual boot I used it go get into Win2kPro when I encountered an impossible-to-circumvent blue-screen-of-death boot crash after installing SP4 - it was lovely). I have XP Pro but have had such a stable experience with Win2kPro that I see no reason to upgrade - yet.

Also certain Malkavian maps would crash when played and/or films viewed on Win2Kpro, but never on WinMe, so I used it while we played those maps. Bizarre but true.

CIK: I'll try out the update as soon as I can.

Posted: **Wed Mar 30, 2005 2:24 pm**

3453 is the only incoming port myth needs (and that's only for hosting), otherwise, allow outgoing connections and you should be good to go.

Posted: **Wed Mar 30, 2005 4:27 pm**

I installed 1.5.1b and it looks like it has fixed my problem. I can use Direct3D now and the framerate looks to be about the same as it was before I started having the problem. Thanks for the fix. What was changed to make it work?

Posted: **Wed Mar 30, 2005 5:57 pm**

That beta works great. Thanks alot.

Posted: **Wed Mar 30, 2005 7:06 pm**

It was a bit of graphics page-locking code in the D3D renderer that Bungie had written then commented out, with a note saying that it interfered with framerate on Voodoo2 cards.

One of the developers, who shall remain nameless, saw that when it was uncommented it slightly improved fps on Win2k and XP (for the most part, varies from system to system). Hence was introduced into the code towards the end of the testing cycle.

Unfortunately as we now know, it screws fps on Win98. The replacement build tests to see if the machine running Myth is Win98ish and if so doesn't do the locking.

Hope that makes sense

Posted: **Wed Mar 30, 2005 10:17 pm**

One of our members that had the slow fps problem on Saturday reports that 1.5.1b fixes it for him. Wh00t!

Question: is it "for sure" that it's not going to be a problem for Win2k/XP on any video card? Just curious as it sounds like the potential gain is not fantastic? Perhaps it should just be commented out for all?

Just playing devil's advocate here...

Posted: **Thu Mar 31, 2005 9:28 am**

It is not for sure. However, from all the information we've received from people, there is no one on XP or 2k yet who has experienced that problem. Furthermore, that approach is also the "recommended" way of doing it according to the API.

tain.totalcodex.net

Direct3D problems - :(