Page 2 of 7 FirstFirst 123456 ... LastLast
Results 11 to 20 of 62

  Click here to go to the first Developer post in this thread.  

Thread: Detonator 81.85

  1.   Click here to go to the next Developer post in this thread.   #11
    Quote Originally Posted by [b
    Quote[/b] ]
    What about all the out of memory? issues,you think those are driver related too? Because -nomap isnt a working solution and it happens on both nvidia and ATI cards, its hard to wait for Aras with a non functional OPFR
    That's a seperate issue, iirc more related to the main system innards than the GPU system operation. A minor little patch I suppose could completely rebuild the entire engine from ground up, replace all the models and textures and maps and other content, and do all sorts of other fun stuff not possible at the time given the several generations earlier hardware at the time, and the development limitations. There's also AGP bus issues you can toss into the mix, and the blame rests squarely on the backs of the video card bosses and mobo manufacturers who show blatent disregard for standards and basic electrical signalling loads.

    Or you could do all that using next-gen tech and methods and call it ArmA.

    Quote Originally Posted by (Heatseeker @ Oct. 22 2005,10:22)
    Cant anything be done? the game is old now but its still very unique and many people like it plus what about VBS1? Is it also afected? Nvidia and Ati should still support the game atleast untill a sequel is made, talk to us Placebo <!--emo& .
    Placebo doesn't work for Nvidia or ATI iirc. How do you suggest that BIS patch an Nvidia driver problem?

    If you troll around on the various news sites and hardware review discussions, and take an aggregate lumping of all the reviews, you'll notice strong trends towards convienently timed driver performance anomolies. Driver re-engineering by third parties has also seemed to confirm that both ATI and Nvidia regularly and deliberately make all sorts of internal 'cheat' optimizations designed to rig the performance of certain Dx or OpenGL calls with certain buffers and timings to achieve marketing advantages in benchmarking.

    This results in increased instability for generic calls, and especially for lower priority prior generation Direct3D calls, as the drivers would be heavily biased to certain D3D 9.0c calls, at the cost of heavy bias against D3D 8.1 calls made directly or wrapped in the 9.0c wrappers.

    Furthermore, in case you've forgotten, when the very first Dx9 5900's and 9800's began to ship, Valve announced the discovery of a critical defect in silicon on both platforms. Both manufacturers, in an effort to upstage each other, had taken a very early beta or pre-beta spec of Dx9 and committed it to silicon. Even the Great Satan of mal-coding Microsoft said that Nvidia and ATI were both brainless idiots for putting buggy beta code onto the chips. That screwup cost another several months delay to Halflife2 while Valve generously implemented a workaround in-game to compensate for the major defects that would otherwise be on those few bleeding edge cards.



    And where is that band that so vauntingly swore, That the havoc of war and the battle's confusion,
    A home and a country shall leave us no more? Their blood has washed out their foul footstep's pollution.
    No refuge could save the hireling and slave, From the terror of flight, or the gloom of the grave;
    And the Star-Spangled Banner in triumph doth wave O'er the land of the free and the home of the brave!
    (3rd stanza of the Star-Spangled Banner)

  2. #12
    The game might be old but its still available for sale, what i was sugesting was that someone might drop the publisher a hint that this problem is happening and maybe, just maybe someone at codies would get in touch with nvidia about this issue, maybe its a small driver
    bug, maybe it could be easily corrected, maybe not, we dont really know.
    Dont know why the big essay ShinRaiden, its all mumbo jumbo to me, forgive my ignorance but i dont see where your heading .
    Its normal that driver developers focus on recent, current gen. products and that older software isnt tested and is droped for dead, unlike you im not willing to let all the work that went into this game go down the crapper while sitting in my ass, patches, addons and mods, code, alot of work was put in the game to make it better and we still dont know who will publish Aras or when it will be released.

    I have seen issues reported at the nzone forums adressed, if all i can do i let them know and hope then thats exactly what i'll do.
    Let nvidia know about it!
    Might make a diference, might not but worth a try, if more people showned support for the game it might increase its odds of not being abandoned.

  3. #13

  4. #14
    had to rollback to 78.01

    i am pretty sure BIS will talk to nvidia about this

  5. #15

  6.   Click here to go to the next Developer post in this thread.   #16
    Quote Originally Posted by (Sch1sm @ Oct. 22 2005,22:45)
    I wouldn't worry about it, i'm having problems with my 6600GT AGP graphics card and i had thought it was an error during the 1.96 patching process that had caused the error. I'm downloading the WHQL 78.01 drivers justnow, even though the 66.93 is recommended for my card.

    Actually, now that i think about it. *Downloads 66.93*

    Also, as far as i know, 1.96 is it. Roll on OFP:E. I'm buying it, and i don't even have an XBOX.
    You're probably going to want newer than 66.93, I had intermittent issues on my 6600gt AGP until 71.89, I'm on 78.03 atm with no complaints in Direct3D or OpenGL, other than M$'s bastardization of 'Open'GL.

  7. #17
    From what i had heard from Placebo's opinions on the NVIDIA ForceWare et. Detonator drivers, it was the 66.93 drivers that supplied the best experience. I stood on my Y2K3 CD lastnight, i was almost in tears. So much so, i made a small poem.

    I had a CD named Y2K3 --
    It cracked! It cracked!
    Windows said it was corrupt --
    It's whacked! It's whacked!
    Why oh why is my CD corrupt?
    Is it simply that Windows is f*cked?

    Will try the 78.03 WHQL.

  8. #18
    RKSL-Rock
    Guest
    Quote Originally Posted by (shinRaiden @ Oct. 24 2005,02:05)
    ...I'm on 78.03 atm with no complaints in Direct3D or OpenGL, other than M$'s bastardization of 'Open'GL.
    Are you running DXDLL with that? ***Because ive been trying different drivers and still cant get it to work with reflections etc on without reducing it to 2-4fps...

    Anyone know a fix? (other than the obvious ...dont use DXDLL)




  9. #19

    Wink

    Quote Originally Posted by (RockofSL @ Oct. 26 2005,14:38)
    Quote Originally Posted by (shinRaiden @ Oct. 24 2005,02:05)
    ...I'm on 78.03 atm with no complaints in Direct3D or OpenGL, other than M$'s bastardization of 'Open'GL.
    Are you running DXDLL with that? ***Because ive been trying different drivers and still cant get it to work with reflections etc on without reducing it to 2-4fps...

    Anyone know a fix? ***(other than the obvious ...dont use DXDLL)
    Hi..

    Same problem for me here.. DXDLL and 78.01 drivers is a no go.. i got 2-4 fps as well

    please tell me what to do..

    thanks..

    NetWalker [1RI] - 1st Regiment of Infantry
    BRAZILIAN OFP, ArmA and ArmA 2 SQUAD

  10. #20
    Switching to ATI will not help, sooner or later no new drivers will support games like OFP.. but we will have OFP2 and AA *** *** Also fog bug and horizon fixes with DXDLL reflections, but FPS 2-5




    "Man is condemned to be free; because once thrown into the world, he is responsible for everything he does."
    -Jean-Paul Sartre

Page 2 of 7 FirstFirst 123456 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •