7 réponses à ce sujet

[ellevi]

the main toolset itself works fine, however oddly enough running the gffeditor or erfeditor returns a "keyfile not found" error. has anyone else encountered this?

[Ynirthotep]

Having the same problem.

[BryanDerksen]

The keyfile system was something we used during beta testing for release security, it was supposed to be entirely removed for launch but I guess something slipped through. However, there's an easy workaround. Instead of trying to run the GFF and ERF editors directly, try opening the GFF and ERF files from the toolset. On my test machine it opens them without complaint that way.

[Fester Pot]

For the beta testing, there was a keyfile sent to each individual which allowed access to the toolset. Perhaps the erf and gff editor packaged with the public release of the toolset is still from the last beta build from the weekend.



I can confirm I'm able to open up the erf and gff editor with the latest beta build.



When I rename the custom dragon.age keyfile sent to us, I receive the following error -



Keyfile not found.



So, it's possible the beta versions were packaged with the public release of the toolset.

[ellevi]

BryanDerksen wrote...

The keyfile system was something we used during beta testing for release security, it was supposed to be entirely removed for launch but I guess something slipped through. However, there's an easy workaround. Instead of trying to run the GFF and ERF editors directly, try opening the GFF and ERF files from the toolset. On my test machine it opens them without complaint that way.

this works great. silly of me not to try that, thanks!

[BryanDerksen]

No problem. Silly of us not to find those remaining keyfile requirements.

[Varenus Luckmann]

BryanDerksen wrote...

The keyfile system was something we used during beta testing for release security, it was supposed to be entirely removed for launch but I guess something slipped through. However, there's an easy workaround. Instead of trying to run the GFF and ERF editors directly, try opening the GFF and ERF files from the toolset. On my test machine it opens them without complaint that way.

Still having issues (see image).

No matter the input at that point, I get the message Unable to edit the file  "<path>" and Reason: Unable to read the ERF file.

Modifié par Varenus Luckmann, 06 novembre 2009 - 09:27 .

[Malcroix]

BryanDerksen wrote...

The keyfile system was something we used during beta testing for release security, it was supposed to be entirely removed for launch but I guess something slipped through. However, there's an easy workaround. Instead of trying to run the GFF and ERF editors directly, try opening the GFF and ERF files from the toolset. On my test machine it opens them without complaint that way.

Fine solution indeed! For those who can actually START THE TOOLSET! I can't, because I have the "cannot connect to database" bug, still not addressed by BioWare.

So either solve the connection to database issue, or give us the keyfile or whatever so we can start GFF/ERF editors independently!