Recognising Newer Graphics Cards for Sims2
|
#341
07-02-2014
I'm glad I didnt offend you, However, What I'm demanding from my graphics card is what it is suppose to do and it wasnt doing it since the game is old and will not run well with good graphics cards due to its old settings. Now that the game and my graphics card are speaking the same lingo, its running smooth.
I wouldnt be troubleshooting if I knew my computer was a toaster, which isnt the case.
I wouldnt be troubleshooting if I knew my computer was a toaster, which isnt the case.
#342
07-02-2014
Boiling Oil.
Actually the first image that Pocketz showed is the lo-resolution, no anti-alias version. It is NOT the hi-texture detail. The change that they made changed her card from Intel which is actually forced to Lo-res version, to use the NVidia which allows a higher resolution. The reason why the grass looks 'hi-texture' is because there is no anti-alias on it. The same as the shore-line which is how ALL shorelines look with Lo-resolution.
While I accept that you were trying to be helpful, I would prefer that you would leave this to me as (a) I have been studying and researching this June 2012, and have been able to resolve many people's troubles - including Intel cards. (b) your advice and opinion was not helpful, and in fact causing more trouble than it was helping.
I don't interfere on your mod threads because I respect that you are more knowledgeable than I am about modding BHAVs. Please show me the same courtesy.
Hi Pocketz,
So sorry about that. You are exactly right to come to get this sorted. I'm sorry you were here during my sleep-time (I'm in Australia) and got such unhelpful replies from BO.
Your original problem was because Intel defaults to Low-resolution by default. I do have a card that fixes that, but since you have a dual card and were able to swap it to the NVidia card that doesn't have that default, it's been fixed.
There is a problem that occurs where the game can't work out the texture memory because Microsoft moved it. If you get a return to Lo-Resolution, I have a fix for that as well, so don't worry - you can have hi resolution regardless.
Actually the first image that Pocketz showed is the lo-resolution, no anti-alias version. It is NOT the hi-texture detail. The change that they made changed her card from Intel which is actually forced to Lo-res version, to use the NVidia which allows a higher resolution. The reason why the grass looks 'hi-texture' is because there is no anti-alias on it. The same as the shore-line which is how ALL shorelines look with Lo-resolution.
While I accept that you were trying to be helpful, I would prefer that you would leave this to me as (a) I have been studying and researching this June 2012, and have been able to resolve many people's troubles - including Intel cards. (b) your advice and opinion was not helpful, and in fact causing more trouble than it was helping.
I don't interfere on your mod threads because I respect that you are more knowledgeable than I am about modding BHAVs. Please show me the same courtesy.
Hi Pocketz,
So sorry about that. You are exactly right to come to get this sorted. I'm sorry you were here during my sleep-time (I'm in Australia) and got such unhelpful replies from BO.
Your original problem was because Intel defaults to Low-resolution by default. I do have a card that fixes that, but since you have a dual card and were able to swap it to the NVidia card that doesn't have that default, it's been fixed.
There is a problem that occurs where the game can't work out the texture memory because Microsoft moved it. If you get a return to Lo-Resolution, I have a fix for that as well, so don't worry - you can have hi resolution regardless.
#343
07-02-2014
UPDATE: It's getting wierder and wierder
terrain seems to missing only with heavy thick snow.Also no snow coverage during daylight at any case and thin layer of snow during the night(where is suppose to be thick snow)
Added config log if needed
KASUTAJA-config-log.txt (Size: 9.86 KB / Downloads: 424)
Thanks in advance!
UPDATE 2:Figured out that shaders and snow are in correlation .Turning shaders off brings back the snow the way it suppose to look.
terrain seems to missing only with heavy thick snow.Also no snow coverage during daylight at any case and thin layer of snow during the night(where is suppose to be thick snow)
Added config log if needed
KASUTAJA-config-log.txt (Size: 9.86 KB / Downloads: 424)
Thanks in advance!
UPDATE 2:Figured out that shaders and snow are in correlation .Turning shaders off brings back the snow the way it suppose to look.
(This post was last modified: 07-02-2014 01:37 AM by Oeselian.)
#344
07-02-2014
OK - I just added a bunch of stuff from HL and put back in ML/Lee's Belhoovan window expansion set. Now I get crashes again... I'm still searching out bad CC - but, those were all fresh DLs, and from reputably wonderful CC creators so it will have to be a CC that's been living in my folder quietly all these years! Is that possible?
Hmmm, my Access_Violation crash log says "System memory: 1024 Megabytes total, 1024 Megabytes free" ...but I have 8 gigs ram plus another gig on my new graphics card. How can it say I have 1024 total, and ALL of it is free? Is that correct?
And, my grass doesn't look nearly as good as theirs in N-Hood view! On the lot, it might look closer - maybe.
Is it possible that the CC/access violation crashes and my graphics card are in cahoots? Or, am I definitely dealing with 2 separate issues here?
Oi! I have a headache. I'm gonna go deep sea diving on the wii. Thank you, Kiri and everyone, for helping me here XOXOXO
Hmmm, my Access_Violation crash log says "System memory: 1024 Megabytes total, 1024 Megabytes free" ...but I have 8 gigs ram plus another gig on my new graphics card. How can it say I have 1024 total, and ALL of it is free? Is that correct?
And, my grass doesn't look nearly as good as theirs in N-Hood view! On the lot, it might look closer - maybe.
Is it possible that the CC/access violation crashes and my graphics card are in cahoots? Or, am I definitely dealing with 2 separate issues here?
Oi! I have a headache. I'm gonna go deep sea diving on the wii. Thank you, Kiri and everyone, for helping me here XOXOXO
Proud member of LeeFish since Sep 2013.
My Etsy shop
My Etsy shop
Time flies like an arrow ~ fruit flies like a banana
Ah, well... there is that
So, ...do you know the difference between roast beef and pea soup?
Ah, well... there is that
So, ...do you know the difference between roast beef and pea soup?
#345
07-02-2014
Oesilian
I agree - the shaders and the snow impact on each other. If you're happy with the shaders off, I'd say stick with that - that's what the code for the Intel card originally had. Let me know if you want to try something else out.
Catherine TCJD
1. The access_violation crash log with the 1024 MB isn't something to worry about, I believe. I think it's more a mismatch between what the game thinks is the memory, and what it actually is. However the game does use more memory than 1G, so I'm currently going with the theory that it's just a reporting issue.
2. Can you do a picture of your N-Hood View, next to a coastline so I can have a look at what you're talking about?
3. CC/Access violation crashes are different to the graphics card problems. But give me an up to date config-log so I can check to make sure.
If you remove HL/Lee's stuff that you added, do the crashes go away?
If not, then it's not the CC.
a. It could be that the hoods been corrupted - depending on how old it is, this is possible. Mootilda has a program that checks for that at MTS (I think?)
b. something else.
If it does, then there are two possible things -
a. one is that you've got a conflict (which would make much sense). The way to test that, is open up your game with JUST HL/Lee's stuff. If it crashes, then there's a problem with your game and that CC.
If it doesn't then you need to get a conflict finder. Now apparently someone in the community has done one that compares the guid rather than just the Checksum. If you can use that - it should be able to track down your conflict.
b. the other is that you are at your upper limit for CC that your game/machine can cope with. You would know if that's the case - how many Gigs of downloads do you have in the game? The problem when you get to that stage is that it does start to corrupt your hood, I believe. What that means is that you would have to do some culling to reduce the load. Using compresser (or whatever it's called that Jfade did) should reduce size, without reducing number. There is also another process - bulking which is combining multiple CC into a single package to reduce the load times, which will also give your game some relief. I believe they have a thread at GoS about it.
Petallotus
Nothings jumping out at me that says why you're not able to change those settings. Are they set off or on?
I agree - the shaders and the snow impact on each other. If you're happy with the shaders off, I'd say stick with that - that's what the code for the Intel card originally had. Let me know if you want to try something else out.
Catherine TCJD
1. The access_violation crash log with the 1024 MB isn't something to worry about, I believe. I think it's more a mismatch between what the game thinks is the memory, and what it actually is. However the game does use more memory than 1G, so I'm currently going with the theory that it's just a reporting issue.
2. Can you do a picture of your N-Hood View, next to a coastline so I can have a look at what you're talking about?
3. CC/Access violation crashes are different to the graphics card problems. But give me an up to date config-log so I can check to make sure.
If you remove HL/Lee's stuff that you added, do the crashes go away?
If not, then it's not the CC.
a. It could be that the hoods been corrupted - depending on how old it is, this is possible. Mootilda has a program that checks for that at MTS (I think?)
b. something else.
If it does, then there are two possible things -
a. one is that you've got a conflict (which would make much sense). The way to test that, is open up your game with JUST HL/Lee's stuff. If it crashes, then there's a problem with your game and that CC.
If it doesn't then you need to get a conflict finder. Now apparently someone in the community has done one that compares the guid rather than just the Checksum. If you can use that - it should be able to track down your conflict.
b. the other is that you are at your upper limit for CC that your game/machine can cope with. You would know if that's the case - how many Gigs of downloads do you have in the game? The problem when you get to that stage is that it does start to corrupt your hood, I believe. What that means is that you would have to do some culling to reduce the load. Using compresser (or whatever it's called that Jfade did) should reduce size, without reducing number. There is also another process - bulking which is combining multiple CC into a single package to reduce the load times, which will also give your game some relief. I believe they have a thread at GoS about it.
Petallotus
Nothings jumping out at me that says why you're not able to change those settings. Are they set off or on?
#347
07-02-2014
I haven't seen your config log for the 8870 - only the Intel. Sorry about the confusion. Can you put that one up, and we'll see what I can do to help.
#348
07-02-2014
Well that's the problem with it.I'm quite sure game uses it(black box shadows,more aa steps,considerably better graphics) but don't recognise it which isn't surprising(Enduro tech) .Hence the odd problem.
Would the it help if I upload my original graphic rules?
Additionally game uses in both modes radeon directx 11 32-bit driver
Driver issue perhaps?
Would the it help if I upload my original graphic rules?
Additionally game uses in both modes radeon directx 11 32-bit driver
Driver issue perhaps?
#349
07-02-2014
There is a driver issue with the directx 11 I think - what build version do you have?
I'm not convinced that it does think it's using the 8870. Even if it is, the settings are being set up by the game assuming Intel. So that would cause problems right there because Radeon/NVidia both have workarounds that Intel wouldn't know about, so they wouldn't be set up.
With the NVidia and a dual card, there is an icon on the tool bar that lights up when its being used. Is that the same for the Radeon? i.e. is there anything in the Radeon menu services that says which card is being used?
Unfortunately, I don't have a dual card on my PC, so I don't know for myself.
I'm not convinced that it does think it's using the 8870. Even if it is, the settings are being set up by the game assuming Intel. So that would cause problems right there because Radeon/NVidia both have workarounds that Intel wouldn't know about, so they wouldn't be set up.
With the NVidia and a dual card, there is an icon on the tool bar that lights up when its being used. Is that the same for the Radeon? i.e. is there anything in the Radeon menu services that says which card is being used?
Unfortunately, I don't have a dual card on my PC, so I don't know for myself.
#350
07-02-2014
Thanks Kiri. I prolly ought to start a new thread? Since this no longer pertains only to graphics rules etc...
What I've gathered so far about the CC issue:
Without HL/Lee's newly DL's CC - I do not crash
With JUST the new stuff - I do not crash
I only crash when the old and new CC are combined
I have just under 5 gb of CC in my game right now (other players with less ram than me report using 10+ gigs CC with no problems other than slow loading times.)
It's all compressorized with JFade's tool. I've just cleaned out my hacks/conflicts with SW/James's HCDU-thingy and BO's help.
The crashes are happening when I'm in the catalog - if that makes any difference?
...also I remember - before I took my sims-break - several years ago, I repriced nearly everything with SW/James' "Sims 2 Categorizer"; then Delphy came out with his DDO - and I learned through discussion of that - James' tool sometimes corrupted objects. After all that work straightening out my catalog *sigh* that's partly what started my taking a break.
I'm beginning to think a pure "Vanilla" game is what I need - but, then I think about all the wondrous completer sets out there...
I will attach my latest config logs - and get a coastline picture for you next time I'm in the game. And I'll run the hood checker too.
I just wanna build!!!
Thanks
ETA: Attachments
What I've gathered so far about the CC issue:
Without HL/Lee's newly DL's CC - I do not crash
With JUST the new stuff - I do not crash
I only crash when the old and new CC are combined
I have just under 5 gb of CC in my game right now (other players with less ram than me report using 10+ gigs CC with no problems other than slow loading times.)
It's all compressorized with JFade's tool. I've just cleaned out my hacks/conflicts with SW/James's HCDU-thingy and BO's help.
The crashes are happening when I'm in the catalog - if that makes any difference?
...also I remember - before I took my sims-break - several years ago, I repriced nearly everything with SW/James' "Sims 2 Categorizer"; then Delphy came out with his DDO - and I learned through discussion of that - James' tool sometimes corrupted objects. After all that work straightening out my catalog *sigh* that's partly what started my taking a break.
I'm beginning to think a pure "Vanilla" game is what I need - but, then I think about all the wondrous completer sets out there...
I will attach my latest config logs - and get a coastline picture for you next time I'm in the game. And I'll run the hood checker too.
I just wanna build!!!
Thanks
ETA: Attachments
Proud member of LeeFish since Sep 2013.
My Etsy shop
My Etsy shop
Time flies like an arrow ~ fruit flies like a banana
Ah, well... there is that
So, ...do you know the difference between roast beef and pea soup?
Ah, well... there is that
So, ...do you know the difference between roast beef and pea soup?
(This post was last modified: 08-02-2014 12:19 AM by CatherineTCJD.)