39 réponses à ce sujet

[dlhotka]

To enable the console add:

[AppDefaults\\\\DragonAge2.exe\\\\transgaming]
"cmdlineadd" = "-enabledeveloperconsole"
To the end of ~/Library/Application Support/Dragon Age II/config


The visible console fix/mod from Origins doesn't appear to work.

[Rimfrost]

Cool, once through the game once I might test it

[KnoxSwift]

Wow, any codes for the console listed yet?
I have to play all characters without cheats first but then it will be time to "play!"

[heemeng]

help!! i installed DA2 in my Mac but I don't see the config file at all, not in the directory stated above or elsewhere. does anyone knows about this???

[Rycr]

Works for me. Thanks a lot! Needed to cheat to get past the final Deep Roads boss since I brought a badly balanced party...

Just a quick note for anyone who can't find the config file. The Library folder you're looking for isn't the one on the root of the hard drive. It's the one in your user folder.

The default key is the Tilde, but that can probably be changed if I could be bothered to hunt for the keybinds file.

[Leounity]

I have done the above several times, but still cannot seem to get the Dev Console to work.

I added the lines to the config, using both TextEdit and Text Wrangler to see if that would work. I then changed the key bindings but no matter what key I change them too the Console won't pop up and I just move around as normal while typing.

This is my first time trying to use the Dev on the mac, my DA:O was for the pc and I was able to get it to work just fine. Am I just overlooking something simple?

Modifié par Leounity, 18 mars 2011 - 07:32 .

[dlhotka]

You don't need to change the key bindings - it just worked on mine (with the ` key, not the tilde).

[Sold Out]

[AppDefaults\\\\DragonAge2.exe\\\\transgaming]
"cmdlineadd" = "-enabledeveloperconsole"

Do we add the whole thing with a space in between the paragraph before? Do we include quotations?

[Sold Out]

This still isn't working for me

[BebopLD]

Also would like any help with this... have come this several times on a PC, followed the listed steps here and on a wiki page exactly and still can't open the console.

Could this be a result of improper spacing or something in the config file? Tried it multiple ways.

[wildx]

Working for me as follows:

(1)

In ~/Library/Application Support/Dragon Age II/config, paste the following code to the end of the file:

[AppDefaults\\\\DragonAge2.exe\\\\transgaming]

"cmdlineadd" = "-enabledeveloperconsole"

(Re paragraphing question: I am not sure if it makes a difference but I did indeed leave a blank line. Common practice when editing code is to copy how the default has been done.)

(2)

Next, go to ~/Documents/BioWare/Dragon Age 2/Settings/KeyBindings.ini, search for the line called OpenConsole_0 and set it to whichever key you like. For me it's:

OpenConsole_0=Keyboard::Button_X

(3)

In game, press X, then start typing runscript etc.

Modifié par wildx22, 11 avril 2011 - 11:45 .

[absolute.territory]

LOL. I don't even have a Dragon Age 2 folder in the Application support section. I have a Transgaming folder... with nothing in it.

Edit: Looked in the wrong folder. Hahaha... anyway, got the console to work. Woo.

Modifié par absolute.territory, 14 avril 2011 - 05:01 .

[dualie11]

Has anybody tried this since the 1.0.2 patch? I have followed these directions to the letter and it simply doesn't work for me. Is there actually supposed to be a drop down console appear, because I get zilch. No error, nothing.

[Crunchyinmilk]

dualie11 wrote...

Has anybody tried this since the 1.0.2 patch? I have followed these directions to the letter and it simply doesn't work for me. Is there actually supposed to be a drop down console appear, because I get zilch. No error, nothing.

It works fine with 1.02.  Either you didn't follow instructions quite to the letter, or you did and your set up is a little obscure (foreign language keyboard) and it doesn't like the default key.

Even with the console enabled you will never 'see' anything.  Wait till you're in game with a character selected, then press the tilde [~] key (by default).  If its working you'll notice none of your keyboard binds work because you're typing in the console.  You won't see any console text because Bioware disabled it in the release version.  Its purely down to memory/touch typing.  

Pressing enter will try to run the command you typed in, and will close the console.  Even if the command is nonsense (like making a typo) the console will close when pressing enter.  You will never see feedback, just results in game.

EG, having Merrill as your active, selected character.  Type:

[~] runscript addtalent 306000 [enter]
[~] runscript addtalent 306001 [enter]

Now when you look at Merrill's abilities screen, she should be able to pick from the Creation tree... (stuff in square brackets = key pressed).

Modifié par Crunchyinmilk, 20 avril 2011 - 07:32 .

[dualie11]

Well, since I'm not exactly a newbie at this sort of thing I'm 100% confident, after checking/redoing it several times, that I did do it properly. And no I don't use a foreign keyboard. I also changed the keybinding several times. Eventually I just went back to the default grave because there is no reason why that shouldn't work.

I did not realize that the console does not actually appear. It is possible that it was working and just didn't realize it. I'll try again, but even after hitting the console key and typing commands I know it wasn't working because keystrokes were causing in game actions.

I'll fiddle with it a bit more and try and get it going. I would really like to fix the Forbidden Knowledge quest. Thanks for the helpful feedback.

[dualie11]

Well, I tried again and nada. I even removed the original config file and let the game generate a new one. I simply paste the two lines in at the bottom and save. I notice Crunchyinmilk that you state that the tilde is the default key. This is not the case in my keybindings. The default is the grave key as the OP (dlhotka) states above "You don't need to change the key bindings - it just worked on mine (with the ` key, not the tilde)." So I don't know why you say the tilde is the default. You must have changed it or you have never checked.

[Crunchyinmilk]

They are one and the same key on my keyboard. I state again, its working for me just fine. I left it at grave, I've just always referred to the key as tilde. An ingrained habit from using the console in Quakeworld.

Regardless, the method works on my mac release, updated to 1.02 as of less than a minute ago... so keep hunting.

[dualie11]

You would have to press the shift key to get a tilde, but yeah they are the same button.

I gave up and went to bed last night. I've done this at least a dozen times now. It simply doesn't work for me for some reason. I'm not using any mods and I have a default install.

This is what the end of the config (of which there is only one for this game, so there's no mistaking it) file looks like:

;; App default settings
;; Ereg
[AppDefaults\\\\eReg.exe\\\\transgaming]
"Disable" = "Y"

[AppDefaults\\\\EACoreServer.exe\\\\transgaming]
"DockIcon" = "N"

[AppDefaults\\\\DragonAge2.exe\\\\transgaming]
"cmdlineadd" = "-enabledeveloperconsole"

[wildx]

Could you have bound the tilde key to something else (in game or otherwise out of game)?

FYI my key binds are

OpenConsole_0=Keyboard::Button_X
OpenConsole_1=(UNASSIGNED)

[dualie11]

I do have the grave key bound in another game, but not in the OS. I have tried other keys, such as x, but nothing seems to work.

I think maybe I'll try deleting preferences. I'm pretty annoyed at this point, because nothing seems to work and I'm running out of options.

[wildx]

Aw sorry to hear. Have you tried it with patch 1.01? Why not try downgrade to 1.01 and see if the console works with that?

[Crunchyinmilk]

 

Modifié par Crunchyinmilk, 22 avril 2011 - 07:44 .

[dualie11]

Thanks Crunchy! I'll try again when I get home from work. I notice that "Grave" is capitalized in your KeyBindings.ini file. It's a long shot, but maybe that will work.

I'm not sure how to downgrade to 1.0.1 without a complete re-install. It may come down to that though. I'll check in later.

[dualie11]

IT WORKED! Believe it or not, I changed the g in "grave" to a "G" and voilà! It worked on the first try. Unbelievable I guess it wasn't a long shot at all.

Thanks a million Crunchy and all those who helped with suggestions! I was finally able to go back and finish the Forbidden Knowledge quest. On the next play through I'll be sure and do it correctly the first time.

[Enziso]

does this still work or no?