Dominus

Is the 'Aiming Deadzone' still in the controls? or has it been removed completely? (I hope it hasn't)

Hiya All, first post. I'm been having nightmares with both my own and brothers pc's with Resistance. We could play with the mission editor just about fine bar one or two crashes/freezes. But the Campaign would could our machines to lock up with either the game just freezing or the screen going BLACK!! Leaving the current sounds/music that were playing looping. REBOOT!!! After installing old/new vga drivers to no avail and changing SWAP setting, defragging etc I have just tried disabling 4x AGP in the BIOS of my pc (PC#1 see below) and it has worked a treat!!! OFPR now runs really smooth, with textures set to 2048x2048 (well there is a few choppy bits in large towns and with some sound effects, notably the motorcycle revs and trebants possibly my soundcard or DX8 acceleration) I suggest anyone suffering freezes to first attempt the VIA fixes, I did, but they haven't worked for me, I am now going to try and disable 4xAGP on my brothers pc tommorow, and will post if it worked. I also tried normal OFP on 2xAGP, it seemed more choppy than when it was on 4xAGP, it looked a lot worse as well compared to OFPR. Maybe there is some problem with old Geforce cards and VIA chipset that OFPR is causing our systems to suffer from again even tho we have apparent fixes for them. Anyhow I'm going to investigate why my hardware cannot run 4xAGP for OFPR but it can for every other game. I MUST have 4xAGP for my new GF4 Ti 4200!!!!! If you have similar specs to those below and are suffering freezes try 2xAGP in your BIOS. Oh and disable any tweaking progs that might try and set your card to 4xAGP( it could cause you more headaches) PC#1 Athlon TBird 1Ghz@10x100 Abit KT7A-RAID 1.1 Mobo - latest BIOS 512Mb Crucial PC133 RAM Hercules GF2 MX 64Mb IBM 40 Gb Hdd Creative SoundBlaster PCI 128 Pioneer 32xDVD-ROM PC#2 Pentium 733Mhz Slot1 Abit VT694X Mobo - lates BIOS 512Mb Crucial PC133 RAM Creative Geforce 256 Pro 32Mb DDR RAM IBM 40Gb Hdd Creative SoundBlaster AWE 64 Value 52xCD-ROM

Albert->If you didn't have any black screen lockup or freezes with OFPR I would leave you AGP aperture size alone mate. I currently have mine set to 64mb which is the motherboard default. And mostly my system is fine, except for a few black screens with other games/demos. I think the problem is some infinate looping problem on some VIA chipsets . I found an article about it once ( I'll have a look for it ). I was always under the impression that the AGP aperture should be set to half of your system ram, in my case 256mb cos i have 512mb RAM, but this caused problems with OFP. Other people have said that modern graphics cards with lots of memory ( ie 64mb or more) dont need a large aperture. And this makes sense if you look at what AGP Aperture is in my mobo manual: </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE"> This option specifies the amount of system ram that can be used by the AGP device. The Aperture is a portion of the PCI memory address range dedicated for graphics memory address space. <span id='postcolor'> Most modern AGP cards with large amounts of ram shouldn't need to use the system ram at all. I dont think changing you AGP aperture will damage anything in your pc, it could just make it unstable with certain games. Recently I thought my Athlon was dead or mobo faulty because it stopped POSTing when run with a 133 fsb. I sorted it though with a bit of research and luck. It turned out that my retailer-unlocked Athlon pencil markings had somehow become worn out even with a sticker over them. I redid the pencil unlocking and tried it, and it worked much to my amazement. But then my IBM hdd died a sudden death, got an RMA from IBM, but it didn't half annoy me!!!!!! If you didn't understand any of that last paragraph, dont worry   , its just an example to show you that pc parts can be more durable than you might think, obviously tho I try to take care of my hardware, and dont try anything risky without reading up on it first on hardware forums.

I overclocked both my Creative Geforce 256 32Mb DDR and my Hercules Gf2Mx 64Mb SDR (never to stupid values, and never for long periods of time), and I resolved the black screens on those cards. So if your card worked fine for other games, its probably not the Gf3. Strangely though, my brother had another black screen crash, the same as with OFP:R, but this was with NeverWinter Nights. It only happened once so far, but Nwn runs like pants anyway on his pc (cpu+mobo upgrade needed). To be honest my bro hasn't played much online OFP:R (thrashing GTA3), but I know for sure he has played it once for an hour or so without any crashes. What similar specs do guys Totala and Munger have? Mobo??

Do you guys have broadband cable?? Or do u use 56K modem for multiplayer ? I assume you have broadband. There might be a conflict with your network card in a particular PCI slot on your mobo. Check you mobo manual. And try another slot. I don't know if it will make a difference with the multiplayer BLACK screen crashes, but worth a try. I was going to try and PCI cards in different slots to try and relieve my games pausing/stutter problem, but until I get a new hdd I can't use my PC. Â Good luck!!

Hmmm interesting Munger, I am using Win98 SE, and I have solved my black screen problems, so you might be onto something there. Keep testing it. I'm really pissed off cos my harddrive has just packed up again. I get Disk I/O Error when I boot now. This has happened before, so I hope I can fix it using IBM Drive Fitness Test.

Glad to hear it has helped you a bit. I had the same BLACK screen crash when I tried multiplayer while the aperture was still 128Mb, but my brother has played a few multiplayer games sine changing it down to 64mb, without any problems. Give it a go and report back. Munger: You still getting the BLACK crash?? For OFPR to run without problems... everthing must be running perfectly methinks....... Good Luck guys

Hmmm, 'tis very strange, Totala. Both my systems haven't had a single crash since changing the aperture, it even stopped crashing on my old Geforce 256 and Geforce2Mx cards, so it doesn't seem to be related to weaker graphics cards, or more powerful cards. BTW, both machines have clean installs of OFP+Red Hammer+OFPR, I also think both systems have had System BIOS caching and Vidoe Bios caching turned off in BIOS, but this might not make a difference. They are definately both off on my system. I'll have to check my bro's. If it crashed on multiplayer could that be caused by the cable modem? or network card drivers? or other programs running in background causing conflicts with netcode ? Totala and Munger: Keep me informed if your get it sorted, I'd like to know what was causing the BLACK screen of death on your systems. Good Luck. I'm really pissed at the moment tho, my bro's weaker system is running games better than mine at the moment, ALL my games seem to suffer from slight update delays, the screen/framerate seems to pause for a second and then carry on, its getting really annoying cos I dont know what it could be. Some question for other techies: 1.Could I have dodgy RAM stick if Windows is reporting that I have 511Mb RAM, instead of 512Mb like my bro's? 2.Or is it my motherboard? Recently my unlocked/overclockable Athlon AXIA 1Ghz (should reach 1.4Ghz quite stable, has done 1.33 in the past) has started to behave erratically. A while ago my system stopped POSTing, and after much fiddling, reseating cpu etc, I found I can no longer run my CPU at 133 front side bus speed, and have to run at its default 10x100 speed. I dont know whether its the motherboard or CPU failing me. I'm wondering if the games framerate pausing is anything to do with the fact that I'm running the CPU at 100Mhz fsb (200mhz ddr for athlon), and the ram at 133Mhz fsb, whereas I would prefer to have both running at 133Mhz fsb (266 Mhz for cpu) like I used to have. Any suggestion other than new cpu and mobo, please. Thanks Good Luck with your systems.

Hiya All, I found that it wasn't AGP2x that was causing my BLACK screen crashes on both of my pc's (mine and bro's) but it was having an AGP aperture size of 128mb in the mobo BIOS. I changed it to 64Mb (both mobo's default settings) and haven't had a black screen (with blue bits) since, or screen freezes/lockups. Current Settings: AGP 4x, 64Mb AGP Aperture Gainward 64Mb GF4 Ti4200 cards. If you have your mobo set to 64Mb Aperture, I don't know what to suggest, other than check you BIOS settings against your mobo manual, it might be caused by using too aggressive memory timings that OFPR just can't cope with. The strange thing is that OFP and Red hammer and all other games installed worked fine with an aperture of 128Mb, the only exception being OFPR. But since changing the AGP Aperture, both systems seem more stable when running games. Munger: Is K7N420 Pro an Nvidia Crush Chipset? Just a guess. If so, the Crush chipset has a built-in Geforce 2 chip doesn't it, maybe theres a conflict there you could look into. Good luck!

Read this thread: Freezes Solved? I was having all manner of screen freezes, and black screen freezes until I reduced AGP aperture size in my BIOS to 64mb. When you get the black screen freeze can you see a thin blue line (like 1 or 2 pixels wide) at the top of the screen? And can you still hear the sound looping in the background? I was getting screen freezes and black screen lock-ups more than crash to desktops, but now OFPR runs fine. BTW, OFP 1.46 worked fine with the original Aperture size (128mb) , but maybe it was pushing my hardware to fast. 64Mb AGP aperture size worked so I'm leaving it at that. Good Luck!!

hiya all, I got my 2 new GF4 Ti4200, some installation problems on PC#2, i think caused by old Creative Geforce Drivers, but fine now. These cards are fast!! However I now think the problem wasn't the 4xAGP setting in the BIOS or RivaTuner (or whatever you use) but more a problem with the AGP Aperture size in the BIOS. I am currently running the new GF Ti4200's with 4xAGP in BIOS ENABLED. And an AGP Aperture size of 64MB Both pc's are running OFPR fine now with no freezes, memory-map problems, or lock-ups, ctd etc. The sound is still a little bit choppy at very few places (namely cutscenes - probably due to hdd loading). N.B The above settings were also used for the old cards, just before the upgrade without problems too. To test this theory I tried to run Tony Hawks 3 demo on PC#1 with an AGP aperture of 256mb (half the systems RAM) and it booted me back to desktop almost instantly with some sort of memory error (sorry can't remember specifics - it was late at night). Has anyone suffering freezes and memory problems tried setting AGP aperture size to 64Mb (or your motherboards default)? I would like to know if this has helped anyone. Gook Luck!!!

If trying updated drivers does not solve your problems take a look at this thread, Freezes Solved? After suffering endless crashes and freezes, I think I have found the solution for my two systems. I REDUCED the AGP Aperture settings in BIOS of both motherboards to 64Mb and haven't had a freeze since. If you still have problems, you may have to bite the bullet and disable 4xAGP in the BIOS too. Not something we want to do, but to play Resistance smoothly, it might be worth it. Good Luck!

Just to update you all, I've tried changing the AGP Aperture size on PC#2 (see previous post above) in the BIOS down to 64Mb, while leaving the AGP4x enabled. Again, it has worked a treat on PC#2. I have just played the campaign from the beginning including all cutscenes, up to mission 2, with textures set to 1024. I can't believe it! not a single problem. No sound loops, crashes, no jitters bar the large towns and busy scenes. I think PC#2's 32Mb of DDR RAM on graphics card really helps it over my SDR Ram on PC#1. So anyone suffering sound problems, crashes, freezes might want to try and reduce their AGP Aperture size to 64Mb. Just got my nw GF4 Ti4200's, gonna try then on both systems and see how far I can push them. Bye for now

I just tried setting my AGP back to 4x in my BIOS. And I noticed something I changed earlier that I forgot to include above... I reduced the AGP Aperture size down to the default 64Mb in BIOS as well. Anyway, 4xAGP and 64Mb aperture isn't perfect, the game still seems to jarr every few seconds, but this could be sound related problems, I hope!!! So those with crashes/freezes might also want ot try setting AGP Aperture size down to 64Mb or whatever your motherboard default is. Good Luck!