6497 réponses à ce sujet

[Dead_Meat357]

And real quick, I've discovered instability in certain parts of the game with Texmod running and I know why. I always use the Wadres Reaper textures which are always in .JPG format. He he managed to make normal maps work like that is beyond me. In any case I'm going to recode them all in one pack, and in the .DDS format.

I'm also going to package the Reaper Husk in with it and I might as well see what I can do on a higher resolution version of the Brute and the Marauder.

Modifié par Dead_Meat357, 20 septembre 2012 - 07:25 .

[ElectronicPostingInterface]

I forgot he did those ships. It's not in the OP anymore so I use Smarteck's.

Yeah, he did a lot of stuff in .jpg for some reason. After switching to optimized files or recoding them myself I noticed stupidly large performance increases. Those .jpg files really do some damage to the game.

[Mrqbasic]

PKchu wrote...

I forgot he did those ships. It's not in the OP anymore so I use Smarteck's.

Yeah, he did a lot of stuff in .jpg for some reason. After switching to optimized files or recoding them myself I noticed stupidly large performance increases. Those .jpg files really do some damage to the game.

Yep, i noticed that at my armor mods for Liara
But somehow im currently not able to do it in .dds, so if anyone is able to convert them, then write me a pm pls
(Only members of our group pls, and no spam)

cheers

Modifié par Mrqbasic, 20 septembre 2012 - 08:21 .

[N7 Lisbeth]

Very strange. I'm having a Texmod problem I simply cannot explain, perhaps someone can lend a technical hand?

It's been a week since I played SP. In that interim I added some new textures, updated some old ones to the newer optimised versions, so I thought, hrmm, maybe too many. So I dropped back to my original number and it crashed after trying to load for 20 seconds. (Usually takes 2-3 minutes with my full texture-load out.) It was the usual "Masseffect3.exe stopped working." So, I figured, let's go back to basics, and disabled even more (including all the new and updated textures - only used the ones I knew worked previously and knew worked concurrently). Still crashes.

I tried repairing, reinstalling, updating, verifying it was large address aware (shouldn't need to do that with ME3 anyway), reverting to original coalesed.bin, reverting to original masseffect3.exe, still having the same crash with anything more than a small handful of textures. My batch file (standard set up) is working fine, Texmod is launching properly, but the error is pretty much inescapable. I rolled back my gamersettings.ini to my backup, still having the same crashing issue. (Running Win7Pro,16Gb of ram and a 2Gb nVidia card. Memory has been checked and it is free, allocatable, and is being used properly in other applications. I've also tried rebooting.) It used to work fine with 20-30 textures. Now I can't run more than 3? What?

Other games work fine. Something happen I wasn't aware of? Anything I'm forgetting?

Summation: Game runs fine vanilla, Texmod launches with 1-3 textures fine. More than a few crashes.

Modifié par N7 Lisbeth, 20 septembre 2012 - 09:13 .

[Dead_Meat357]

What I've done so far is added a normal map to the Husk which it was missing. I also did a new light map for it. The texture is the same one Smartek did. I've lumped those in with the Banshee and Cannibals which were done by Wadres. They were recoded and added together. I'll probably have to add teh Brute and the Marauder later. They will take a very long time to fix. Actually, I'm testing something out on the Brute right now. If it looks good I'll throw it in.

I've also recoded the Reaper Destroyer that Wadres did. Fantastic mod if you haven't seen it. Link incomming soon.

Wadre's Reaper Destroyer

Modifié par Dead_Meat357, 20 septembre 2012 - 10:03 .

[Dead_Meat357]

FXAA tool would cause crashes and lockups for me on some system configurations with Mass Effect 3. I abandoned it's use for that reason long ago.

But yeah, I used a couple of Wadres's mods fairly regularly and I had issues in specific parts of the game. Rannoch, etc. and I'm fairly certain it's due to those mods. I've improved the Husk with a normal map and I'm adding it to the Banshee and Cannibal mod. I'm about to test changes to the Brute, so we'll see how that goes.

Modifié par Dead_Meat357, 20 septembre 2012 - 10:47 .

[Fredy AG]

Dead_Meat357 wrote...

I've also recoded the Reaper Destroyer that Wadres did. Fantastic mod if you haven't seen it. Link incomming soon.

Wadre's Reaper Destroyer

but that Destroyer was already optimized in Skydrive (only 19MB) long time ago. 

skydrive.live.com/


///////

Modifié par smarteck, 20 septembre 2012 - 11:13 .

[Dead_Meat357]

smarteck wrote...

Dead_Meat357 wrote...

I've also recoded the Reaper Destroyer that Wadres did. Fantastic mod if you haven't seen it. Link incomming soon.

Wadre's Reaper Destroyer

but that Destroyer was already optimized in Skydrive (only 19MB) long time ago. 

skydrive.live.com/


///////

I guess I missed that one then.

[Dead_Meat357]

Iveybella wrote...

Huh, maybe the settings were too high, I had some problems with it on my old computer but it seems to work okay on my new one

But I can't wait to see the brute, I don't think anybodys done one one yet

The Brute is not a forgiving texture. I'll have to work on it when I've got more time. Anyway, the Reaper collection volume 1 is inbound shortly. I didn't include the Marauder or the Brute. Just the Banshee, Cannibal and Husk. These are the same textures you've seen before, but the Husk now has a normal map and it didn't before. That's my only contribution. That and lumping all the files together.

The Reaper Troop Collection Volume 1

Includes Husk (Texture by Smartek) (Normal and light map by Dead_Meat.)
Includes Banshee and Cannibal by Wadres.

Modifié par Dead_Meat357, 20 septembre 2012 - 11:38 .

[Fredy AG]

Iveybella wrote...

Huh, maybe the settings were too high, I had some problems with it on my old computer but it seems to work okay on my new one

But I can't wait to see the brute, I don't think anybodys done one one yet

I've made ​​some progress on that ... 

social.bioware.com/forum/1/topic/368/index/9735492/104#13647579


//////

Modifié par smarteck, 20 septembre 2012 - 11:59 .

[McRileyW]

N7 Lisbeth wrote...

Very strange. I'm having a Texmod problem I simply cannot explain, perhaps someone can lend a technical hand?

It's been a week since I played SP. In that interim I added some new textures, updated some old ones to the newer optimised versions, so I thought, hrmm, maybe too many. So I dropped back to my original number and it crashed after trying to load for 20 seconds. (Usually takes 2-3 minutes with my full texture-load out.) It was the usual "Masseffect3.exe stopped working." So, I figured, let's go back to basics, and disabled even more (including all the new and updated textures - only used the ones I knew worked previously and knew worked concurrently). Still crashes.

I tried repairing, reinstalling, updating, verifying it was large address aware (shouldn't need to do that with ME3 anyway), reverting to original coalesed.bin, reverting to original masseffect3.exe, still having the same crash with anything more than a small handful of textures. My batch file (standard set up) is working fine, Texmod is launching properly, but the error is pretty much inescapable. I rolled back my gamersettings.ini to my backup, still having the same crashing issue. (Running Win7Pro,16Gb of ram and a 2Gb nVidia card. Memory has been checked and it is free, allocatable, and is being used properly in other applications. I've also tried rebooting.) It used to work fine with 20-30 textures. Now I can't run more than 3? What?

Other games work fine. Something happen I wasn't aware of? Anything I'm forgetting?

Summation: Game runs fine vanilla, Texmod launches with 1-3 textures fine. More than a few crashes.

I had the same problem and I just patched texmod with LAA. Large Address Aware and the problem is gone now.

texmod was written in 2009. Man, the code is fine but needs updates.

[McRileyW]

Dead_Meat357 wrote...

Long answer:


Short answer: 

No.

Thank you for the explanation. Well, I have to give up now. Thought loading DDS would be a good idea too. Saving the tpf-unpack time. But well, guess I can just have a cup of coffee while the game is loading now.



EDIT:

Anyone tried uMod yet? http://code.google.com/p/texmod/

It can load tpf files on the fly. That means no more waiting before the game starts. However, I found out that some tpf could make uMod crash, and it lagged a bit during the in-game loading. I believe if your PC is powerful enough maybe the game won't lag.

At present, it doesn't work for me *yet* to make uMod load DDS only.  

Modifié par McRileyW, 21 septembre 2012 - 02:10 .

[N7 Lisbeth]

McRileyW wrote...

I had the same problem and I just patched texmod with LAA. Large Address Aware and the problem is gone now.

texmod was written in 2009. Man, the code is fine but needs updates.

I thought you had it, I really did. I totally overlooked setting LAA on Texmod this time around and when I looked, it was set to False. But after switching it to True, I still couldn't load all my usual textures. I have managed a way to get most of them, but I have no idea why I suddenly have such a lowered limitation to begin with.

I'll be the first to say one of the new ones I started using (before this broke) was a 50Mb armour .tpf, but it worked fine with more loaded than I can launch now. Just weird.

I wonder if I should tag it with forced Win98 compatibility.

Edit: That is so bizarre. If I mix the order they're loaded in, it loads fine. ??? That's going to bother the neat-freak in me, since all of my stuff is categorises into armour, clothes, cosmetics, monsters, npcs, squadmates, structures, and weapons. <Shakes head> Windows7. <Hands on hips> Oh, you.

Modifié par N7 Lisbeth, 21 septembre 2012 - 01:06 .

[Dead_Meat357]

N7 Lisbeth wrote...

McRileyW wrote...

I had the same problem and I just patched texmod with LAA. Large Address Aware and the problem is gone now.

texmod was written in 2009. Man, the code is fine but needs updates.

I thought you had it, I really did. I totally overlooked setting LAA on Texmod this time around and when I looked, it was set to False. But after switching it to True, I still couldn't load all my usual textures. I have managed a way to get most of them, but I have no idea why I suddenly have such a lowered limitation to begin with.

I'll be the first to say one of the new ones I started using (before this broke) was a 50Mb armour .tpf, but it worked fine with more loaded than I can launch now. Just weird.

I wonder if I should tag it with forced Win98 compatibility.

Edit: That is so bizarre. If I mix the order they're loaded in, it loads fine. ??? That's going to bother the neat-freak in me, since all of my stuff is categorises into armour, clothes, cosmetics, monsters, npcs, squadmates, structures, and weapons. <Shakes head> Windows7. <Hands on hips> Oh, you.

The loading order is actually something we've always had to contend with. Though it used to produce blacked out textures when they didn't work.

[McRileyW]

Dead_Meat357 wrote...

The loading order is actually something we've always had to contend with. Though it used to produce blacked out textures when they didn't work.

The funny thing is that my textures will become transparent if they don't work -- especially transparents banshees in MP ... Man, that is a nightmare XD

Modifié par McRileyW, 21 septembre 2012 - 02:06 .

[N7 Lisbeth]

Dead_Meat357 wrote...

The loading order is actually something we've always had to contend with. Though it used to produce blacked out textures when they didn't work.

ME1 and ME2, I never ran into barriers or limitations. ME3 only when I basically replaced everything all at once, forcing me to separate 15-30 textures/mods per act. Never had to worry about the order until today, I always just que'd them in alphabetical order.

So what's the key to the order? Not grouping large files together? Staggering the large files seemingly worked, but I've had a very limited exposure to this issue so clarification is always welcome.

Modifié par N7 Lisbeth, 21 septembre 2012 - 02:50 .

[Xaijin]

You need to set your max tex size to 4096 in coalesced.

[N7 Lisbeth]

Xaijin wrote...

You need to set your max tex size to 4096 in coalesced.

Definitely have that set still. (The gamersetting.ini isn't affected by repairs or reinstalls, the directory is unrelated to game data. I did restore it, but added that and a few other essentials back in.)

Modifié par N7 Lisbeth, 21 septembre 2012 - 06:23 .

[Dead_Meat357]

McRileyW wrote...

Dead_Meat357 wrote...

The loading order is actually something we've always had to contend with. Though it used to produce blacked out textures when they didn't work.

The funny thing is that my textures will become transparent if they don't work -- especially transparents banshees in MP ... Man, that is a nightmare XD

Different graphics cards and settings could cause different behavior in regard to this. I can tell you that I got blacked out textures on my Radeon HD 7970. On my dual GTX 680 setup I haven't had the issue, so I'm not sure how it would look. I'm not looking forward to ever finding out. I queue up about 50 mods these days at a time. I've combined some to make them easier to manage. One thing is for certain, once I downloaded optimized versions, or optimized the files done by Wadres myself, I haven't had any problems.

[Dead_Meat357]

N7 Lisbeth wrote...

McRileyW wrote...

I had the same problem and I just patched texmod with LAA. Large Address Aware and the problem is gone now.

texmod was written in 2009. Man, the code is fine but needs updates.

I thought you had it, I really did. I totally overlooked setting LAA on Texmod this time around and when I looked, it was set to False. But after switching it to True, I still couldn't load all my usual textures. I have managed a way to get most of them, but I have no idea why I suddenly have such a lowered limitation to begin with.

I'll be the first to say one of the new ones I started using (before this broke) was a 50Mb armour .tpf, but it worked fine with more loaded than I can launch now. Just weird.

I wonder if I should tag it with forced Win98 compatibility.

Edit: That is so bizarre. If I mix the order they're loaded in, it loads fine. ??? That's going to bother the neat-freak in me, since all of my stuff is categorises into armour, clothes, cosmetics, monsters, npcs, squadmates, structures, and weapons. <Shakes head> Windows7. <Hands on hips> Oh, you.

Is there a mod you use specifically each and every time? Was it updated recently? Have you done anything with graphics drivers, or any other drivers on the machine? Is Windows set to download drivers? The last thing you'd ever want is for Windows to update drivers on it's own.

[N7 Lisbeth]

Dead_Meat357 wrote...

Is there a mod you use specifically each and every time? Was it updated recently? Have you done anything with graphics drivers, or any other drivers on the machine? Is Windows set to download drivers? The last thing you'd ever want is for Windows to update drivers on it's own.

Let Windows update on its own? That's crazy talk. I'd delete Adobe entirely if it didn't have a "never check for updates" option. Oh, Adobe flashplayer, that I never used and never installed, how I do not miss your update spam.

But no, nothing changed that week other than what I mentioned (one new mod and some filename restructuring -- which changed the order they were loaded in). I will say, it did make me realise just how big some of the mods I've been using have gotten. Have you ever noticed the HR Citadel mod is like 75Mb? My N7 Femshep armour (none of the ones in this thread) is 49Mb. That's one of the mods I recently downloaded. I can make it work, just requires order juggling. Once I figure it out, I'll just rename files with a load order so I can ctrl-a them as usual.

Consequently, I haven't seen a blackened texture since ME1, and then only on the weapon workbench. In ME2, I wouldn't, but instead I got some occasional texture bleeds when I used the weapon mod workbench. In ME3, I get none of that and instead get startup errors. Same version of Texmod between all three, hah.  (Three copies of the same file; I extracted from the zip three times for simplicity in browse-selection directory recall.)

In any event ... Sorry for the Texmod digression. I kinda/sorta got it worked out.

Modifié par N7 Lisbeth, 21 septembre 2012 - 08:22 .

[Metalunatic]

I have a problem.

I have been using about 50-60 different .tpf files with texmod, which are in total a bit under 1GB in size, while loading ME3 and I keep getting crashes when loading a game from the main menu or in-game after playing for less than a minute -- depending on how many files I have loaded.

I have used LAA on ME3.exe and Texmod.exe. I haven't changed the load order. I changed the max texture size in coalesced.

Specs -- Windows 7/64bit, Core i7 260k 3.40ghz, HD 6990, 16GB DDR3

Maybe it happens becouse I have too many files loaded? Any helpful advice is welcome.

[McRileyW]

@ N7 Lisbeth & Metalunatic

Have you tried removing FXAA? Today I didn't have the problem in ME2 (with 8 tpf-s loaded) until I used FXAA. I have removed FXAA by now and will test the game later.