464 réponses à ce sujet

[Iron Spine]

----------------------------------------------------------------------------------------------------------


UPDATE 3-12-2010@7:07PM CST
I have a new 6+ month contract cranking up that takes me across the country, so v1.0.0.32B will likely be the last version of the editor. It is not fully where I wanted it to be, but I believe it is functional enough to be used as intended. It was a fun project and I enjoyed it a lot.

UPDATE 3-12-2010@7:55AM CST

v1.0.0.32B

- The stripped CR's produced by the native RTB control are now replaced on output so the mod file is notepad friendly.

- The main edit box has been slightly modified so it hopefully stands out more clearly as the main edit area.


Always check the bug posts for the latest known bugs or to post those you encounter:
http://social.biowar...iscussion/1290/



----------------------------------------------------------------------------------------------------------
CED
Project and Download can be found here:
social.bioware.com/project/1854/#details

Partial Features List can be found here:
social.bioware.com/project/1854/discussion/1388

A few screen shots can be found here:
social.bioware.com/project/1854/#gallery

How to start a new game as fast as possible:
social.bioware.com/project/1854/discussion/1358/

----------------------------------------------------------------------------------------------------------
DEBUG LOGS
For v13+, issues experienced with the application should use the following topic to post the contents of generated logs for troubleshooting.
social.bioware.com/project/1854/discussion/1339/

DEFAULT COALESCED
If you find yourself in need of the original v1.00 file look here:
Disk 2 in data01.rar/BioGame/Config/PC/Cooked

A default v1.01 Coalesced.ini can be found here:
http://social.biowar...ct_file_id=3037

----------------------------------------------------------------------------------------------------------
GROUPS
Groups that I become aware of related to ME2 and modding will be put here:

Mass Effect 2 - .ini Modders
http://social.bioware.com/group/1579/

Texture Modders Group
http://social.biowar...scussions#group

----------------------------------------------------------------------------------------------------------
ADDITIONAL TOOLS:

The following tools or code will be of interest to those looking to further disect or modify other aspects including models and graphics.

This one is in the early stages and in source-code form for those that wish to assist the author in analysis or just like looking at code.

Simple ME2 TLK dumper project can be found here:
social.bioware.com/project/1919/

These can be used to extract .PCC and possibly other files. There is (currently) no known repacker/rebuilder for PCC files. Let me know if you find or create one.

Unreal Package Extractor:
http://www.gildor.or...del/extract.zip
Unreal Package Decompressor:
http://www.gildor.or.../decompress.zip
Skeletal Mesh Editor:
http://www.gildor.or...mp/SkelEdit.rar

Dedicated Coalesced Fixer:
Useful to anyone that wants to edit the file manually, and would also be useful to anyone building automation scripts that need to insert a rebuild somewhere.
social.bioware.com/forum/1/topic/106/index/869923

REFERENCE MATERIALS

Driveninhifi wrote...
Here's some info about Unreal packages from Tim Sweeney (epic's lead programmer):
unreal.epicgames.com/Packages.htm
If the pcc are just these guys, this may help. Unfortunately the format seems to be quite complex, which will make packing them annoying without more documentation.
However, the free Unreal Dev Kit may help:
www.udk.com/download

----------------------------------------------------------------------------------------------------------
MISC USER PROJECTS
In this section I will post links to interesting projects related to ME2 that are brought to my attention. If you know of one or own one that you'd like listed shoot me a note and I'll check it out.

Thanks to user skan5 for the link to the project containing v1.01 ini file. The project space itself seemed interesting to me as well looks like DemonSlayer_1 is having a good time with ME2:
http://social.biowar...ect/2052/#files

----------------------------------------------------------------------------------------------------------
MANUAL OVERRIDES

If you don't want to use the editor, you can change some settings by using an override file GamerSettings.

You override some settings in Coalesced.ini by using (adding or changing) the options you want in GamerSettings.ini in your default location, such as:

U:/Users/YourUserName/Documents/BioWare/Mass Effect 2/BIOGame/Config/GamerSettings.ini
(Note this is a Vista location. Just find yours where good old XP kept them. Probably Documents and Settings been awhile would have to pull up a VM to look)

So, for example, if you want to change some of the settings in the Coalesed.ini file here's a procedure you can follow after backing up Coalesced.ini and GamerSettings.ini

( 1 ) Open Coalesced.ini in a Notepad++ tab
( 2 ) Open GamerSettings.ini in another Notepad++ tab.
( 3 ) You have 2 tabs open now that you can cycle between the files.
( 4 ) In Coalesced locate the following section: [SystemSettings]
( 5 ) You see a ton of settings.
( 6 ) Notice this same section in GamerSettings tab. It has a minimal list.
( 7 ) Locate the entries in Coalesced tab you want to change and copy the entire entry line.
( 8 ) Select GamerSettings tab and paste that line or lines under the last entry under [SystemSettings]
( 9 ) Do NOT duplicate any entries that already exist in GamerSettings. [SystemSettings] section.
( 10 ) Save GamerSettings.ini
( 11 ) No changes were made to Coalesced.ini
( 12 ) Run the game and see your new settings take affect.

And that's it.

What's being done here is very simple. The game uses all the settings from the Coalesced.ini file as default settings. However, you can simply override some of these settings by doing what I just described.

I have confimed the [SystemSettings] changes as described above works perfectly. I set UseVsync=False as well as the SmoothedFrameRate=False in GamerSettings.ini and upon loading my previously locked rate of 60 went to 400fps. So this procedure should work just fine.

Also note for your own experiments you can copy an entire section content into the GamerSettings.ini file and simply comment-out all the entries you just pasted into it and slowly uncomment the ones you want to change or play with. The only known (to me anyway) section that works for certain when overriding settings in this manner is [SystemSettings] because I use the Coalesced editor for most tasks now and it's growing so I no longer bother with GamerSettings at all.

To comment-out an entry in an ini file just prefix it with a semi-colon ;

Example:

[SystemSettings]
Resolution=_1920x1200
... other entries removed for clarity
UseVsync=False

would turn off VSync.

[SystemSettings]
Resolution=_1920x1200
... other entries removed for clarity
;UseVsync=False

would NOT turn off VSync because UseVsync is commented-out, and the default value for that key in Coalesced.ini is True, not False.

Ok enjoy hopefuly this will help some folks have an easier time at customizing their Mass Effect 2 experience as they see fit, for performance reasons or anything else.

----------------------------------------------------------------------------------------------------------
USER CONTRIBUTIONS:

I have been exploring potential commands and the FLY command is a better choice than Ghost in some cases, as it will allow the character to asend vertically over objects where as ghost will simply pass through objects. So it'll depend on why you're using it in the 1st place. If you're using it to get un-stuck then a combination of both should be able to get you out of just about any stuck condition, including toggling it off then back on after you fall for a bit if at a great height and trying to get down.
-Iron


An excellent workaround for the common issue of getting stuck inside / ontop of models and terrains.

zBobG wrote...

On the PC version of ME2 you can add a binding for a "noclip" function. I've used this a couple of times to rescue my player from floating.

[SFXGame.SFXGameModeDefault]
Bindings=( Name="NumPadFour", Command="Ghost" )
Bindings=( Name="NumPadFive", Command="Walk" )

"Ghost" allows the player to walk away from the area that has a floating error, "Walk" puts the player back on the ground when you get to a safe place.

And you can go further and make it a single key like this:

Iron Spine wrote...

Bindings=( Name="Add", Command="Ghost | OnRelease Walk")

Holding the key turns on noclip. Releasing the key turns it off.

And for some crazy fun, chew on this one:

Iron Spine wrote...

Look at this beauty.

( Name="Shared_Action", Command="Exclusive Used | TryClimbOrMantleCover | Exclusive TryAcquireCover | OnRelease StormOff | OnHold 0.2 StormOn | OnTap 0.3 TryExitCover 1" )

They have an excellent system. Based on my reading of this you can effectively chain together a litteral infinite number of functions or actions to a key. You simply need to know them, and if they have a result value returned or if not (void). Very nice.

The command for screenshot has been located. Note the following:

Emperor Iaius I wrote...

The binding for the screenshot feature is called "shot"--just set one of the keys to it.

nota bene: screenshots will not work while you are engaged in dialogue.

pyide wrote...

Oh nevermind. I can add new binds just fine to the ini in notepad++,
ex: Bindings=( Name="LeftControl", Command="shot" ) to take screenshots with left control under [Engine.PlayerInput], save, then open the ini in your program and rebuild and it works. Thanks man, this thing will come in handy!

Modifié par Iron Spine, 13 mars 2010 - 01:10 .

[zacrobmer]

Your ideas are good but your thought process is wrong, Guinness should never be served Ice Cold.

[Iron Spine]

zacrobmer wrote...

Your ideas are good but your thought process is wrong, Guinness should never be served Ice Cold.

lol... I hate warm beer, but I love Guinness. So it's just fine for me. If I ever go overseas then I'll just have to deal with it warm on their turf. But since I'm in my home office, I'll take it cold, thanks

[zacrobmer]

Lol I didn't say warm, just not ice cold! However Guinness is Guinness, it's good either way!


Edit: and to stay somewhat on topic to your post.... In your digging around the.ini files did you see anywhere the workaround for the lack of a screenshot function?

Modifié par zacrobmer, 29 janvier 2010 - 06:34 .

[Iron Spine]

zacrobmer wrote...

Lol I didn't say warm, just not ice cold! However Guinness is Guinness, it's good either way!


Edit: and to stay somewhat on topic to your post.... In your digging around the.ini files did you see anywhere the workaround for the lack of a screenshot function?

Very true. Domestic beer taste like baking soda to me. But not the big G. Good stuff, strong impact.

EDIT: I didn't yet since I was actually just after a way to turn off the vsync and flares as part of my testing but then quickly realized other folks don't know this yet and might still be driving themselves insane with byte-count worries in Coalesced so I posted this thread as soon as that thought crossed my brain.

I'll take a quick look and see what I find.

UPDATE: The command is call shot and it's been added to the user contribution section..

Modifié par Iron Spine, 09 février 2010 - 02:40 .

[zacrobmer]

Iron Spine wrote...

zacrobmer wrote...

Lol I didn't say warm, just not ice cold! However Guinness is Guinness, it's good either way!


Edit: and to stay somewhat on topic to your post.... In your digging around the.ini files did you see anywhere the workaround for the lack of a screenshot function?

Very true. Domestic beer taste like baking soda to me. But not the big G. Good stuff, strong impact.

EDIT: I didn't yet since I was actually just after a way to turn off the vsync and flares as part of my testing but then quickly realized other folks don't know this yet and might still be driving themselves insane with byte-count worries in Coalesced so I posted this thread as soon as that thought crossed my brain.

I'll take a quick look and see what I find.

Awesome, I have yet to take a look at the .ini files been to busy playing.

Amen to the domestic statement (Micros/macros aside there are some greatlocal breweries out there!) and is why I brew my own.

[SWAGLE NUTS]

lol, ok besides booze!



this sounds interesting, and looks like it might do the trick, i didnt like editing Coalesced.INI in the first place, ill try this when i get home and post results

[eclipsez0red]

well done 5 stars



seems exactly like config/autoexec.cfg situation except for the fact that config.cfgs arent byte limited

[Iron Spine]

SWAGLE NUTS wrote...
lol, ok besides booze!
this sounds interesting, and looks like it might do the trick, i didnt like editing Coalesced.INI in the first place, ill try this when i get home and post results

Ok good deal when if I get  chance here in a second I'll look around for mouse settings and see if my procedure will knock that problem out or not. I also noticed you posted about the Storm speed and that's a by-design feature. I assume they did that so we can't use running too effectively, like being able to just dart all over the place like a rabbit, as part of game difficulty / realism. But anyway that bugs me too but not because I want to do that in combat. It's because I want to get across my ship faster. Low attention span and all. I'll dork around with Storm later and see if can manage any changes to it.
 

eclipsez0red wrote...
well done 5 stars
seems exactly like config/autoexec.cfg situation except for the fact that config.cfgs arent byte limited

Thanks hopefully this will help some people, those having issues they need to tweak to get around, and those simply wanting to tweak for what-ever reason. We'll see how it goes. This is all very preliminary and if I encounter anything that debunks/doen't-work using what I said I'll update the original post with it.

[eclipsez0red]

EDIT: THIS IS NOT WORKING

mouse damping has returned

heres what your gamersettings.ini is gonna look like after youve modified your mouse stuff

i have tried this myself it works

in fact my mouse response feels better than before

might not work 100% with changing mouse sensitivity tho im uncertain mouse feels good but

i cant seem to be able to adjust my mouse sensitivity

had to leave mouse sens out of gamersettings and change it in coalesced

[SystemSettings]
Resolution=_1920x1200
ResX=1920
ResY=1200
QualityBloom=True
FilmGrain=False
MotionBlur=False
DynamicShadows=True
LightEnvironmentShadows=True
MaxCharacterCinematicLightingPasses=3
EnableLightEnvSHLights=True
MaxAnisotropy=8
BorderlessWindow=False
Fullscreen=True
DepthOfField=False
UseVsync=False

[SaveGames]
Location=

[AppCompat]
MeasuredCPUScore=300.485321
CompatLevelComposite=3
CompatLevelCPU=5
CompatLevelGPU=3
GPUVendorID=4318
GPUDeviceID=1504

[IniVersion]
MouseSensitivity=0.20
bEnableMouseSmoothing=false

[SFXGame.BioPlayerInput]
bUseMouseDampening=false

[SFXGame.BioSFHandler_PCConversation]
AccumulationDivisor=500.0f

Modifié par eclipsez0red, 29 janvier 2010 - 07:58 .

[Deinonychus]

Hmm, I notice an entry called "WeaponsUseHeat=false" in Coalesced.ini.



Has anyone tried changing this to true and testing it out?

[Nezacant]

zacrobmer wrote...

Your ideas are good but your thought process is wrong, Guinness should never be served Ice Cold.

I have to disagree.  Guinness should only be served ice cold.  Not ice cold =

[sticks435]

Deinonychus_Z wrote...

Hmm, I notice an entry called "WeaponsUseHeat=false" in Coalesced.ini.

Has anyone tried changing this to true and testing it out?

I did. I can't remember off hand, it either did nothing, or caused the game to load to a blank screen with the menu music playing, and I had to force kill it. I'm guessing this is kinda like ME1, where a bunch of setting were left over from development, and they didn't bother to take them out until much later.

[eclipsez0red]

i cant seem to be able to adjust my mouse sensitivity

had to leave mouse sens out of gamersettings and change it in coalesced

Modifié par eclipsez0red, 29 janvier 2010 - 07:55 .

[robevans89]

Too bad copying over the console key section doesn't make the console accessible in game.

[eclipsez0red]

one thing it works for is vsync

[Iron Spine]

Yep it's not as straight forward as it could have been for the mouse. The mouse settngs are not affected as noted in my update. Still experimenting with a few things to see if it's possible.

[zBobG]

I tried this method yesterday with various sections to see if they can be overridden. It may be that only some sections (like [SystemSettings]) can have overridden entries.

I tried to add some key bindings to the GamerSettings file and they were completely ignored. I tried some modifications in other sections and none worked. You may have noticed that the Coalesced.ini file is just a bunch of other .ini files stuck together, I even recreated the .ini files separately in the "Cooked" folder and in the "Config" folder then added a traceable modification, that didn't work either.

So, anything in [SystemSettings] can probably be overriden easily by using the GamerSettings file but aparently the only sure way to override other settings is by editing the Coalesced file.

The Console: There is (or was) a debug version of the game executable, it may only be available to the developers. It's possible that the console may only be present in that debug version and that it has been removed from the release version of the game.

[Iron Spine]

zBobG wrote...

I tried this method yesterday with various sections to see if they can be overridden. It may be that only some sections (like [SystemSettings]) can have overridden entries.

I tried to add some key bindings to the GamerSettings file and they were completely ignored. I tried some modifications in other sections and none worked. You may have noticed that the Coalesced.ini file is just a bunch of other .ini files stuck together, I even recreated the .ini files separately in the "Cooked" folder and in the "Config" folder then added a traceable modification, that didn't work either.

So, anything in [SystemSettings] can probably be overriden easily by using the GamerSettings file but aparently the only sure way to override other settings is by editing the Coalesced file.

The Console: There is (or was) a debug version of the game executable, it may only be available to the developers. It's possible that the console may only be present in that debug version and that it has been removed from the release version of the game.

Yep I've been chewing the file and created a BioInput earlier to see if it picks it up but of course it doesn't. This is very annoying for those trying to tweak their settings. Bio should really chime in on these and help folks out that are battling with ther sensitivity settings.

[SWAGLE NUTS]

Iron Spine wrote...

SWAGLE NUTS wrote...
lol, ok besides booze!
this sounds interesting, and looks like it might do the trick, i didnt like editing Coalesced.INI in the first place, ill try this when i get home and post results

Ok good deal when if I get  chance here in a second I'll look around for mouse settings and see if my procedure will knock that problem out or not. I also noticed you posted about the Storm speed and that's a by-design feature. I assume they did that so we can't use running too effectively, like being able to just dart all over the place like a rabbit, as part of game difficulty / realism. But anyway that bugs me too but not because I want to do that in combat. It's because I want to get across my ship faster. Low attention span and all. I'll dork around with Storm later and see if can manage any changes to it.
 

eclipsez0red wrote...
well done 5 stars
seems exactly like config/autoexec.cfg situation except for the fact that config.cfgs arent byte limited

Thanks hopefully this will help some people, those having issues they need to tweak to get around, and those simply wanting to tweak for what-ever reason. We'll see how it goes. This is all very preliminary and if I encounter anything that debunks/doen't-work using what I said I'll update the original post with it.

wow thanks, i get the feeling that if people like you worked for bioware. . . .well we probably wouldnt even have threads like this

oh and also i understand that storm shouldnt turn as fast as regular movement, i just figured it should at least have enough turning that you can choose whether you hit a certain cover or not

Modifié par SWAGLE NUTS, 29 janvier 2010 - 08:55 .

[Iron Spine]

SWAGLE NUTS wrote...

Iron Spine wrote...

SWAGLE NUTS wrote...
lol, ok besides booze!
this sounds interesting, and looks like it might do the trick, i didnt like editing Coalesced.INI in the first place, ill try this when i get home and post results

Ok good deal when if I get  chance here in a second I'll look around for mouse settings and see if my procedure will knock that problem out or not. I also noticed you posted about the Storm speed and that's a by-design feature. I assume they did that so we can't use running too effectively, like being able to just dart all over the place like a rabbit, as part of game difficulty / realism. But anyway that bugs me too but not because I want to do that in combat. It's because I want to get across my ship faster. Low attention span and all. I'll dork around with Storm later and see if can manage any changes to it.
 

eclipsez0red wrote...
well done 5 stars
seems exactly like config/autoexec.cfg situation except for the fact that config.cfgs arent byte limited

Thanks hopefully this will help some people, those having issues they need to tweak to get around, and those simply wanting to tweak for what-ever reason. We'll see how it goes. This is all very preliminary and if I encounter anything that debunks/doen't-work using what I said I'll update the original post with it.

wow thanks, i get the feeling that if people like you worked for bioware. . . .well we probably wouldnt even have threads like this

oh and also i understand that storm shouldnt turn as fast as regular movement, i just figured it should at least have enough turning that you can choose whether you hit a certain cover or not

Well thanks for the compliment but the procedure won't work for mouse settings because they didn't include an automatic pick-up / priority look-up in their code. What I mean by that is, the Coalesced file is a series of embedded configuration files, each denoting its byte length in the headers. So think of it as a big file with other files compacted into it, but instead of being encrypted they are simply in plain english but have a strict length that must be equal to that specified in the header.

Anyway so what should be possible, but isn't, is to create the file seperately on disk and have the game pick that file up (look-up) and use the settings specified therein, overriding the settings in the compacted version. But it doesn't appear Bio has done that. So without that capability the file itself has to be edited

Modifié par Iron Spine, 29 janvier 2010 - 11:56 .

[NewZealand]

Thanks so much Iron Spine, i have been able to edit the graphics using the file and therefore been able to play the game alot easier with less lag.

[syklonis01]

I figured this out myself a couple days ago, should have posted here..but the lack of a search function is mind-boggling here yet again! You'd think from day one that you'd have a search, same thing happen with dragon age. Over abundance of same threads...



http://forums.guru3d...ad.php?t=314216

[shadow.85]

so has any1 figured out how to increase visual quality with Min and Max LOD detail for each texture group under [systemsettings] ???



I have been trying for ages to no avail, maybe some1 with more graphic knowledge can do it?

[Kru12000]

Thanks all and eclipsez0red for your settings. I was going crazy trying to get this bloody game running smoothly. Now I can play at my monitor's native rez without horrible stuttering and slowdown. Cutscenes are no long out of sync too.

Man, after Dragon Age I wasn't expecting ME2 to perform this horribly out of the box.