Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Becareful while Testing Dx10

13»

Comments

  • The user and all related content has been deleted.

    "Freedom is just another name for nothing left to lose" - Janis Joplin
    image

  • openedge1openedge1 Member Posts: 2,582
    Originally posted by solareus


    The only fact is this :
     
    You can go and on about my hardware and brush this off , the only fact that is remained in this entire thread is that the issue is there, and with the wrong combination of hardware and drivers , it will get the next users. Hope people who are not suched up into Funcoms a-hole can get some information out of all the posts of this thread regarding the state of the game and the community. I'm done with this topic, discuss away.

    None of what you said makes any sense. Sorry. But, I still need to point these out to you

    Defective GPU's

    http://www.techspot.com/news/31222-nvidia-losing-money-over-defective-gpus.html

    More defective GPU's

    http://www.joystiq.com/2008/08/12/rumor-nvidias-defective-gpu-woes-worsen/

    I still believe THIS is your issue, and not some "space" in a "map" from unconnected "vertices" 

    Good luck mate

     

     

  • GuRu39GuRu39 Member UncommonPosts: 58

     

      There was a reported incident during the middle of last year that someone had let the game kick back out to the login screen and left the computer unattended and the core teperature of the video card went to the 180 range and burnt up the card.

      Where this game is concerned, it could be any number of things to do with the way the engine manipulates the driver/hardware to a faulty fan on the video card (Funcom Is Aware of this Rumor).

      While I personally do beleive the situation is possible, I would try and replicate the issue again to have a valid test case for the developers to look at, saying that they will.. One incident of this is freaky, but more than one would have some validity to it and show a possible flaw in the game or engine. If you can replicate this , then I would definately send the info to Funcom Support and give them the information and the location of the Playfield error. It would take a major patch to repair the playfield and I do not think that with the next few deployments they would make it game breaking enough to change it without proof.

     

     

     

     

     

     

  • JackdogJackdog Member UncommonPosts: 6,321

    Can't believe they are still having problems after all this time. I played with the DX10 on the test server back in February and it was hardly ready for prime time. Looks like Funcom is getting desperate and figures this is a way to attract players into coming back. I have a feeling this game is losing money still.

    I miss DAoC

  • kdw75kdw75 Member UncommonPosts: 73

     I have been running AOC after signing back up and I am very happy with it. Sure is a much more fun game than Warhammer which I tried right after it. I also like it at least as well as WOW. The bugs are really cleaned up since I left after my first month back at release. I am running in DX10 with everything set to the max except some of the detail distances and it runs about 70 FPS most of the time and my video card is only running about 70C while F@H keeps my video card at 75C. This game isn't even working my video card as hard as F@H so how could this damage it? I don't buy it.

  • SuttonianSuttonian Member UncommonPosts: 65
    Originally posted by solareus


    The only fact is this :
    Which is bad coding on the client. Never seen this kind of error, only in map leaking, because there is nothing in the negative space.

    Everything inside the map as some kind of allocation to the memory, everything has its place. When a leak accures , a vertex or vertices is not connected, opening a hole to all of the negative area out side of the grid. Some driver and cards may be able to fill this whole with a kind of patch but, for some reason, my card (NOT OC'D by ME ) and driver combination showed the uncoonected vertex and went ahead to rendered the negative space, and for the zone of Ymir, who knows how big this -space was. Able to get screenshots was a bit dangerous on my point and should of know better to just shut it down, but hopping to help fix a mapping error with a visual image may help the mapper see what is happening with the object that should be placed there. Another aspect is that is is a modeled object , and in dx10 again with my card and driver rendered as negative area, Either way, the dx10 client with my nvidia 8800GT and the latest driver from nvidia, detected it.
     
    You can go and on about my hardware and brush this off , the only fact that is remained in this entire thread is that the issue is there, and with the wrong combination of hardware and drivers , it will get the next users. Hope people who are not suched up into Funcoms a-hole can get some information out of all the posts of this thread regarding the state of the game and the community. I'm done with this topic, discuss away.

    What you posted in your screenshots is not a leak. It is simply a region of the screen not being cleared. A 'leak' usually refers to a situation where memory keeps being allocated but not freed. Multiple renderings to the same texture do not consume memory.

  • The user and all related content has been deleted.

    "Freedom is just another name for nothing left to lose" - Janis Joplin
    image

  • openedge1openedge1 Member Posts: 2,582
    Originally posted by solareus


    cool, when i went back to the location in dx9 I saw what was there, and was surprised that is was an mob frozen in ice. That also got me thinking that is was more texture then mapping. You make a great point with this information. My card acted unexpectly upon seeing this object in dx10, so it very well could of been a hardware issue at that point in time after  2 years of owning one of the most stable videos cards I've ever used.
    Not shallow enough to deny any possiblity, though to me it looked like  map leakand my gpu didnt like it :).
    My warning stands though "be careful while testing this stuff"

    I agree.

    The lesson here is clean your hardware at least once a week of dust, or repercussions can follow for any game that drives these peripherals to their limits.

    Cheers

Sign In or Register to comment.