2549 réponses à ce sujet

[Mstark]

CDAMJC wrote...

FitScotGaymer wrote...

@CDAMJC

I really do think that the (crashing) problems people are having with this mod is probably the latest update from Nvidia borking something with the GC drivers.

I think this because I had this mod installed with Texmod, then with ME3 explorer, and then a fresh install with the Exe and it all ran fine no crashes up until a few weeks ago. And I reckon that may coincide with an update from Nvidia.

I didn't find the crashes prolific enough to really interfere with my enjoyment of the game. It would runs fine for the most part.

So for that i really wanted to say thanks for your hard work. And thanks also for all the troubleshooting you have attempted to do for those of us who got a bit stuck.

My only regret is there isn't (yet) an ME2 mod like this that runs not using Texmod. I never realised just how long the game takes to launch using texmod. Jeez.

Thank you for your appreciation and support

I thin it both NVidia and AMd recent updates.  It is because of the new driver architecture guaranteed.  I tried rolling my AMD drivers way back to 13.1 and the game runs fine, unfortunately some others games don't like 13.1.  Previously I had tried only 13.4 drivers not 13.1 when I rolled back.  Found on the latest drivers I was getting much less infrequent but still happening crashes on ME2 as well.  Guess these games are now past their shelf life on newer hardware

[pigosso]

CDAMJC wrote...
The launch.int isn't changed since 2008 so it should be the same across all versions mine says = Mass Effect for all possible values. And it says Mass Effect in the task bar.

LAUNCH.INT IS CHANGED

EDIT: and so, half the files present in the INT folder (which however i'm not qualified to discuss about their change)

EDIT2: i repacked your mod with 7-zip... and the actual dimensions are.. 2.7GB
i wouldn't complain about everything.. but that's about the 46% your installer is

Modifié par pigosso, 28 août 2013 - 03:19 .

[Catechrism]

Okay I see the difference, in my case I have re-installed everything and now my local.int matches your original widescreen fixer still crashes, I cannot explain that. The int file is simply a file that shows possible error messages and what name shows at the bottom of the screen, it doesn't effect widescreenfixer at least in my testing. In the new version of the installer I'll remove all of those files, because they are not necessary for the mod to work.

As for repacking with 7zip, amazing find!! I will put up a torrent using that with the latest version once its done and also maybe I can add it to moddb as a single download.

[pigosso]

CDAMJC wrote...

Okay I see the difference, in my case I have re-installed everything and now my local.int matches your original widescreen fixer still crashes, I cannot explain that. The int file is simply a file that shows possible error messages and what name shows at the bottom of the screen, it doesn't effect widescreenfixer at least in my testing. In the new version of the installer I'll remove all of those files, because they are not necessary for the mod to work.

As for repacking with 7zip, amazing find!! I will put up a torrent using that with the latest version once its done and also maybe I can add it to moddb as a single download.

well, i was looking for what widescreen fixer or flawless widescreen were better, and since you said flawless widescreen is better (source? otherwise i trust you ) i'll use that (and thanks god the original launch.int fixed its crashes)

-btw widescreeen fixer was meant to be used only with 1.02 steam version (and so, probably, your crash)-


and i tried several setting on 7 zip. the one i used was 192MB dictionary, 273 word, block dimension solid and LZMA2 algorithm
but probably, if you increase even more the dictionary (i couldn't for memory problems) the final size will be even lower
ps torrent would be awesome
if you would like to upload the mod on moddb too, remember that 7zip format natively support file splitting

Modifié par pigosso, 28 août 2013 - 06:05 .

[Catechrism]

pigosso wrote...

CDAMJC wrote...

Okay I see the difference, in my case I have re-installed everything and now my local.int matches your original widescreen fixer still crashes, I cannot explain that. The int file is simply a file that shows possible error messages and what name shows at the bottom of the screen, it doesn't effect widescreenfixer at least in my testing. In the new version of the installer I'll remove all of those files, because they are not necessary for the mod to work.

As for repacking with 7zip, amazing find!! I will put up a torrent using that with the latest version once its done and also maybe I can add it to moddb as a single download.

well, i was looking for what widescreen fixer or flawless widescreen were better, and since you said flawless widescreen is better (source? otherwise i trust you ) i'll use that (and thanks god the original launch.int fixed its crashes)

-btw widescreeen fixer was meant to be used only with 1.02 steam version (and so, probably, your crash)-


and i tried several setting on 7 zip. the one i used was 192MB dictionary, 273 word, block dimension solid and LZMA2 algorithm
but probably, if you increase even more the dictionary (i couldn't for memory problems) the final size will be even lower
ps torrent would be awesome
if you would like to upload the mod on moddb too, remember that 7zip format natively support file splitting

Awesome thanks for your help, and if the original .int fixed your crashes I am defintely removing it from the installer to avoid issues like this.  I will get a new version out ASAP, maybe tonight even.  In it I have fixed the eye glow people were complaining about, used a real iris for the eye texture, so the eyes look real now, fixed the overwrite issues, I'll remove all inecessary int and shader files I've learned about including this issue, and I've added a pretty cool medley of ME music to the installer so you have something to listen to while it installs I think it makes it feel really polishes so I'm pretty pleased with it. 

I am still working on Avina, Russian subitle fix, dlc fixes which I am awaiting programmer assistance in MEExplorer and some armors, which will all have to come later in the third instalment because I want to remove all of these glitched first.  I will aim for today or tomorrow release if all goes well.

As for why flawless widescreen is better, I was reading the fixes (HUD, cut-scene, and view angle) it covers that widescreen fixer doesn't on the widescreen fixer page, the link I attatched earlier will take you there.  Also I say it's better because its not limited to Steam only.

Modifié par CDAMJC, 29 août 2013 - 07:23 .

[Ghostwise]

CDAMJC wrote...

I can't get widescreenfixer to work at all I have no idea why, but I was able to find this: which works quite well with the mod : flawless widescreen 

By the way, do you guys know if the "bottom half of the screen cannot be screen-capped during cinematics when using certain unclear NVidia resources" bug has new solutions ?

I tried everything I could find two years back - usually involving deactivating the vignette or post-proc - without success, but maybe somebody had a bright idea since then.

[Mstark]

So I have some info.  During all my attempts to solve the CTDS I was getting from ME1 I noticed that  large number of people started reporting the same issue out of the blue about 3 - 4 weeks ago.  Just like me most of them had been able t run the game and now it was unstable as hell.  So I have been contacting EA and finally got a response, this was over  the phone so to paraphrase: 

"We are aware of the recent problems people have and launching mass effect and the crash to desktop issues.  The cause is recent updates to both windows  operating system and hardware drivers and we have no plans to fix the issue for a game released in 2007.  The game will not run properly on some modern hardware configurations and is not considered compatible with windows 8.  While some users may not have issues, others will and nothing will be done.  No further patches will be released for mass effect."

So in essence the game has ran its shelf life and these crashes are most likely NOT A PROBLEM WITH YOUR MOD.

[Catechrism]

Mstark wrote...

So I have some info.  During all my attempts to solve the CTDS I was getting from ME1 I noticed that  large number of people started reporting the same issue out of the blue about 3 - 4 weeks ago.  Just like me most of them had been able t run the game and now it was unstable as hell.  So I have been contacting EA and finally got a response, this was over  the phone so to paraphrase: 

"We are aware of the recent problems people have and launching mass effect and the crash to desktop issues.  The cause is recent updates to both windows  operating system and hardware drivers and we have no plans to fix the issue for a game released in 2007.  The game will not run properly on some modern hardware configurations and is not considered compatible with windows 8.  While some users may not have issues, others will and nothing will be done.  No further patches will be released for mass effect."

So in essence the game has ran its shelf life and these crashes are most likely NOT A PROBLEM WITH YOUR MOD.

Thanks for this valuable info.  This is sad, looks like we'll have to try to fix it ourselves over time, hopefully its something we the modding community can fix, I'll do my best to look into possible fixes but all help is appreciated.

[pigosso]

Ghostwise wrote...

CDAMJC wrote...

I can't
get widescreenfixer to work at all I have no idea why, but I was able to
find this: which works quite well with the mod : flawless widescreen 

By
the way, do you guys know if the "bottom half of the screen cannot be
screen-capped during cinematics when using certain unclear NVidia
resources" bug has new solutions ?

what program are you using? i think you could give a try to MSI afterburner
never heard about this problem btw..

EA says...
"We are aware of the recent problems people have and launching mass effect and the crash to desktop issues.  The cause is recent updates to both windows  operating system and hardware drivers and we have no plans to fix the issue for a game released in 2007.  The game will not run properly on some modern hardware configurations and is not considered compatible with windows 8.  While some users may not have issues, others will and nothing will be done.  No further patches will be released for mass effect."

butttt.... i haven't heard of any other game broken by this "(in)famous" windows/drivers updates
i would differently explain the increasing of the complains with the release of the new texmod-free version (which i think is way more usable and popular)

i feel this is only EA's pass-the-buck policy
i heard of thousand of games "not optimized for windows 8" but if i was able to play need for speed underground 2, gta vice city, and many even older buggy games on my windows 64 bit, i don't think why an unreal engine 3 games shouldn't succeed

Modifié par pigosso, 29 août 2013 - 10:33 .

[Mstark]

pigosso wrote...

EA says...
"We are aware of the recent problems people have and launching mass effect and the crash to desktop issues.  The cause is recent updates to both windows  operating system and hardware drivers and we have no plans to fix the issue for a game released in 2007.  The game will not run properly on some modern hardware configurations and is not considered compatible with windows 8.  While some users may not have issues, others will and nothing will be done.  No further patches will be released for mass effect."

butttt.... i haven't heard of any other game broken by this "(in)famous" windows/drivers updates
i would differently explain the increasing of the complains with the release of the new texmod-free version (which i think is way more usable and popular)

i feel this is only EA's pass-the-buck policy
i heard of thousand of games "not optimized for windows 8" but if i was able to play need for speed underground 2, gta vice city, and many even older buggy games on my windows 64 bit, i don't think why an unreal engine 3 games shouldn't succeed

Funny thing was I discovered that even vanilla me 1 and me2 were having problems for me now where I have never had any issues and no other issues at all.  This mod stressed the engine and made the crash more common but it was still happening on vanilla just not as often that led me to start looking farther and I found a trove of others having the same issue scattered around forums.  So yes it is EA passing the buck as there is something with their version or the unreal engine that is having problems ( AS bioware modified the engine for both games).  Sad but alas it is some things are working for some but not others, steam and origin versions of the game are not installing properly and refuse to launch for most people and the GPF crashes are very common now so there was some change not just this mod use that led to the issue, one sight said the 1.02 patch was installing correctly and origin confirmed this as well, it is all just a cluster job and no one is goig to fix it

[Ghostwise]

pigosso wrote...

what program are you using?

ME1's own tiled shot function - the bottom half of the screen is entirely blacked out on such shots. You can see the issues pop up with some frequency on forums back in the ME1 days, but I don't think it's a common one. As I said disabling vignette and/or post-prod did the trick for most, but not for me.

I can presumably use SweetFX to take big .bmp screenshots during cinematics so it's not a serious problem.

But since there are apparently new mods dealing with the rendering of in-game cinematics I thought I'd ask knowledgeable folks if that rings a bell.

[pigosso]

Mstark wrote...

pigosso wrote...

EA says...
"We are aware of the recent problems people have and launching mass effect and the crash to desktop issues.  The cause is recent updates to both windows  operating system and hardware drivers and we have no plans to fix the issue for a game released in 2007.  The game will not run properly on some modern hardware configurations and is not considered compatible with windows 8.  While some users may not have issues, others will and nothing will be done.  No further patches will be released for mass effect."

butttt.... i haven't heard of any other game broken by this "(in)famous" windows/drivers updates
i would differently explain the increasing of the complains with the release of the new texmod-free version (which i think is way more usable and popular)

i feel this is only EA's pass-the-buck policy
i heard of thousand of games "not optimized for windows 8" but if i was able to play need for speed underground 2, gta vice city, and many even older buggy games on my windows 64 bit, i don't think why an unreal engine 3 games shouldn't succeed

Funny thing was I discovered that even vanilla me 1 and me2 were having problems for me now where I have never had any issues and no other issues at all.  This mod stressed the engine and made the crash more common but it was still happening on vanilla just not as often that led me to start looking farther and I found a trove of others having the same issue scattered around forums.  So yes it is EA passing the buck as there is something with their version or the unreal engine that is having problems ( AS bioware modified the engine for both games).  Sad but alas it is some things are working for some but not others, steam and origin versions of the game are not installing properly and refuse to launch for most people and the GPF crashes are very common now so there was some change not just this mod use that led to the issue, one sight said the 1.02 patch was installing correctly and origin confirmed this as well, it is all just a cluster job and no one is goig to fix it

origin and steam crash the first time you launch the game, are known problems from ages, which simply require you run the game as an administrator for the first time
secondly, make sure you have 1.02 patch installed
and third, try some older nvidia drivers (which i read should be way more stable than newer ones)
if you are on ati, just use latest 13.8beta2

[2112.rush]

I have a problem installing the mod.

I downloaded all 9 parts from ModDB, extracted them all into the same folder and ran the exe. Directed the installer to my Mass Effect install directory and waited. However, when it was almost finished it asked for "part10", which I cannot find.

EDIT: After some digging, I think I may have gotten a corrupted file. Redownloading and I will post results.

EDIT 2: Yep, corrupted file. All straightened out now. Awesome mod! Thanks for all of the hard work.

Modifié par 2112.rush, 31 août 2013 - 08:18 .

[PR_]

Wow, i just got ignored. Great.

[Catechrism]

2112.rush wrote...

I have a problem installing the mod.

I downloaded all 9 parts from ModDB, extracted them all into the same folder and ran the exe. Directed the installer to my Mass Effect install directory and waited. However, when it was almost finished it asked for "part10", which I cannot find.

EDIT: After some digging, I think I may have gotten a corrupted file. Redownloading and I will post results.

EDIT 2: Yep, corrupted file. All straightened out now. Awesome mod! Thanks for all of the hard work.

Glad you got it sorted out thanks for liking the mod

[pigosso]

PR_ wrote...

Sorry, i already read the trouble section and nothing helped me. I installed with the .exe and nothing happened so i put the folder directly into the ME folder, i think it's working, but some things are strange, the shadows for example, i did the 0.03 thing and cleared the cache after dowloading the shadow fix, but i still have the block shadows. I don't know what to do.

have you downloaded the shadow fix?

[marcosfish]

I had no luck here: as soon as the game starts, while I'm still at the Bioware logo intro, it freezes. When I alt+tab, there's this message:



Any ideas? Running it on Windows 7 64-bit.

Modifié par marcosfish, 01 septembre 2013 - 06:53 .

[Catechrism]

marcosfish wrote...

I had no luck here: as soon as the game starts, while I'm still at the Bioware logo intro, it freezes. When I alt+tab, there's this message:



Any ideas? Running it on Windows 7 64-bit.

Unused mip errors are a typo or invalid entry in the bioengine.ini 90 percent of the time, the other 10 would be a bad install.

Modifié par CDAMJC, 01 septembre 2013 - 08:49 .

[Catechrism]

Hello everyone I have uploaded a torrent version of the newest version of the mod with some fixes and a few updates right now I am the only seeder but hopefully once people finish we can have lots of seeders and a good dl speed, I will upload the non-torrent files throughout today but it will take some time for uploading and approval etc...

Torrent version here, details are in the description: link

Modifié par CDAMJC, 01 septembre 2013 - 09:03 .

[marcosfish]

CDAMJC wrote...

Unused mip errors are a typo or invalid entry in the bioengine.ini 90 percent of the time, the other 10 would be a bad install.

Thanks for the answer.
Your tip led me to remember I had renamed two of the intro movies (the files themselves, not on bioengine.ini), in order to skip them. So I renamed both to their original names and it worked.

I played for 10 minutes only, but it looks pretty good !

[NyashkaKun]

Text in the installer can not read

[Catechrism]

Quick test everyone I may have uploaded a glitch load femshep face 3 freckles in a new character or if you already have that character. Is her face black?

[Catechrism]

Yep I uploaded a bug femshep face 3 isn't being rendered, fixing now, please refrain from downloading until I update, sorry to everybody who downloaded yesterday and today

To fix the bug you'll need to re-download,

or get the latest svn of ME3Explorer. Run it and open ME1Explorer, find texture: "HMF_HED_PROCustom_Frek_Diff"
right click hover over fixes and apply the no render fix and save changes that will solve the issue quicker than re-downloading the entire mod, but if that's a bunch of gibberish to you just wait to re-download the mod.

[Catechrism]

Okay fixed files uploaded just awaiting authorization.

Edit: Authorized, download away!

Modifié par CDAMJC, 03 septembre 2013 - 07:52 .

[Catechrism]

Nooo! I am sorry I ticked a 64-bit option in the compression section of the mod thinking it would use more of my system ram to compress to get the files size down, looks like it was a setting for a 64-bit windows app only i will fix it but I gave to work to day so it should be up in about 12 hours or so.