Aller au contenu

Photo

WARNING: Patch v1.04


31 réponses à ce sujet

#1
Sunjammer

Sunjammer
  • Members
  • 925 messages
Patch v1.04 contains an old version of script.ldf i.e. that from v.102 or patch001.erf as it is also known.

Basically if you like the new functionaility we got with v1.03 don't touch v1.04. If you are not sure what the new functionality is see my New Scripting Commands thread.

#2
Nathan Willis

Nathan Willis
  • BioWare Employees
  • 69 messages
Hello, a quick note here: I've taken the information Sunjammer has posted and am forwarding it along to the devs. Apologies for the inconvenience, and thanks to Sunjammer for the quick catch.

#3
Sunjammer

Sunjammer
  • Members
  • 925 messages
I'm currently testing a quick work-around: I'm dropped an extracted v1.03 version of script.ldf into the [Program Files]\\Dragon Age\\packages\\core\\patch\\ folder. The missing functions have been returned to the function list my scripts still appear to compile okay. Next step is run a few in-game tests.

If you are looking for the v1.03 version of script.ldf you can find it in the patch002.erf in the above folder.

Modifié par Sunjammer, 19 juillet 2010 - 05:57 .


#4
dan107

dan107
  • Members
  • 850 messages
Does this affect in any way anyone that's just playing the regular version of the game (no mods, etc.)?

#5
DLAN_Immortality

DLAN_Immortality
  • Members
  • 481 messages
Should we wait for patch 105, then??

#6
Sunjammer

Sunjammer
  • Members
  • 925 messages

dan107 wrote...

Does this affect in any way anyone that's just playing the regular version of the game (no mods, etc.)?

Playing? I doubt it. Modding? Very much so.

DLAN_Immortality wrote...

Should we wait for patch 105,
then??

I'd suggest waiting for a response from BioWare, which failing until we have a better understanding of what was affected and how we can work-around it.

#7
DLAN_Immortality

DLAN_Immortality
  • Members
  • 481 messages
Yes, before I install any patch I have to really know what it "breaks".



It´s always a bit harder for people who are making mods with the toolset because so many things can go wrong.



If you did try it with the toolset already, Sunjammer, please let me know if it´s safe or if it will break things.



Another question is that I modify certain dlgs from the Single Player campaign. Does this patch fix anything in any dlg?



Thanks. :-)

#8
Galatean

Galatean
  • Members
  • 72 messages
Well, if it's only an accidental reversion, then your workaround should function flawlessly.

If, however, it was rolled back on purpose, then there might be problems. I doubt that, however. They're far more likely to have placed a new version-tag if the rollback was on purpose.

So, until the hotfix comes out, your workaround should be fine.

Still, remember everyone: if you're going to use the workaround, backup.

Modifié par Galatean, 19 juillet 2010 - 07:36 .


#9
Sunjammer

Sunjammer
  • Members
  • 925 messages
BioWare confirmed last night that the inclusion of the old script.ldf was unintentional. There was an issue that allowed out of date files into the build. BioWare thought this had been corrected but it appears at least script.ldf slipped through. I suspect, given how focussed the patch was on in-game stuff, it is likely only the toolset is affected. In any event, if you've updated, keep an eye out for any m2da driven properties that might be missing a few options.

Additionally this morning I noticed a comment from another modder who wasn't using the work-around saying that he was getting a bunch of compiler errors when he tried to compile scripts. There wasn't any more detail so I'm going to remove the work around and do some more testing.

#10
DLAN_Immortality

DLAN_Immortality
  • Members
  • 481 messages
Well, I'm too paranoid to install patches right after their release. I always wait for others to be the guinea pigs... :-)



With what I´m reading I think I´ll wait for a re-release or another patch... maybe not in my lifetime, but eh. Still, I rather wait than have so many toolset problems.



Thank you! :-)

#11
-Semper-

-Semper-
  • Members
  • 2 256 messages
good to know that there's always the nwn2 toolset around :D

#12
Firkraag8

Firkraag8
  • Members
  • 10 messages
So if I get this correctly this has nothing to do with the game itself, and only affects modders? I was about to replay DA and see I came in a good time with the new patch. If it only affects modders then I'll start right away.

#13
Guest_werwulf222_*

Guest_werwulf222_*
  • Guests
Thanks for the info and the workaround. As a Steam user and newbie modder, I'll have to remember to always play offline until I want the new patch.

Modifié par werwulf222, 21 juillet 2010 - 05:17 .


#14
DLAN_Immortality

DLAN_Immortality
  • Members
  • 481 messages
Any news about an official fix that works for this issue?

I mean, it kind of sucks to still have patch 103 because I use the toolset...

#15
DahliaLynn

DahliaLynn
  • Members
  • 1 387 messages
Unfortunately, I have installed 1.04 already, and fear that the problems I am experiencing are related.

Loading a relatively simple cutscene, with every action I make, the toolset locks for a few seconds, and then allows me to continue, as if some sort of memory overload. I realize there could be causes for this I am unaware of, (perhaps not 1.04?) but I have gotten used to the editor working smoothly, and now, find it almost impossible to work with.

My mind will be more at ease if I know it is at least working properly so that if there are any problems that arise such as these, I could try to solve them knowing that the probem is on my end.

Sunjammer please let us know if you or bioware has found a fix for this old script problem, as I simply loathe (if not fear accidental loss of work) reinstallation!

Thanks so much!

Modifié par DahliaLynn, 25 juillet 2010 - 07:01 .


#16
FergusM

FergusM
  • Members
  • 460 messages
Dahlia, the cutscene editor tends to slow down very quickly with speak line events or headtracking, if that helps at all. I usually add them last.

#17
DahliaLynn

DahliaLynn
  • Members
  • 1 387 messages
Oh yes I am familiar with that :) No this slow down/temporary lock-up was much more than a headtracking issue. I am used to the general slowdown and adjust accordingly. This was unlike anything I have experienced before, *with* full headtracking and speakline.

If I were to go into the details of the specs of each scene and their differences in attributes, I might find an answer. I just want to be sure it is within my control, and not caused by the "old scripting" issue.

If I would know this, then at least my reasoning would be an educated reasoning, and not a reasoning that stemmed from a faulty program.

(I once spent half a year (1999)  trying to figure out why my pro-audio card was causing sync issues, popping, and other problems. I deeply researched every possible software fault, setting, conflict or hardware inconsistency. When I finally gave up I had called the Audio card company itself and they told me that according to my serial no. the card itself was a faulty card, and they would replace it. I mistakenly assumed the card was fine all along)   

Modifié par DahliaLynn, 25 juillet 2010 - 01:06 .


#18
Sunjammer

Sunjammer
  • Members
  • 925 messages

DahliaLynn wrote...

Sunjammer please let us know if you or bioware has found a fix for this old script problem, as I simply loathe (if not fear accidental loss of work) reinstallation!

There is a work-around described in my second post: I've been using it without noticing any side-effects so far. If that changes obviously I'll post about it.

I've also tested compiling and running scripts that don't use the new functions without the work-around and again I haven't had an issue so far.

DahliaLynn wrote...
If I were to go into the details of the
specs of each scene and their differences in attributes, I might find
an answer. I just want to be sure it is within my control, and not
caused by the "old scripting" issue.

I can't see how an old language definition file would have any effect on a custscene. However there may be other old files the patch003.erf that might affect cutscenes.

Modifié par Sunjammer, 25 juillet 2010 - 02:37 .


#19
DLAN_Immortality

DLAN_Immortality
  • Members
  • 481 messages
But the question is... will Bioware address this issue or will they leave it to the fans to fix their problems???



I'm a bit bugged with that... it's basic support. They messed it up, where is their fix??

#20
DahliaLynn

DahliaLynn
  • Members
  • 1 387 messages

FergusM wrote...

Dahlia, the cutscene editor tends to slow down very quickly with speak line events or headtracking, if that helps at all. I usually add them last.


Ok Fergus,

I must add a strange fact. I turned off accurate headtracking. It smoothed the workflow. The reason I was so against doing this was because I had worked on a previous scene with tons of headtracking, along with accurate headtracking enabled, and I hadn't experienced such a major change as I do now. Hence, I still don't get why here it's super slow and in my previous scene, it flowed so much better. Not to mention that the previous scene was also much longer. :blink:

Anyway, thanks.

#21
DLAN_Immortality

DLAN_Immortality
  • Members
  • 481 messages
Bump. Where's the fix, Bioware? ¬_¬

#22
-Semper-

-Semper-
  • Members
  • 2 256 messages
you are waiting for toolset support? poor being^^

#23
DahliaLynn

DahliaLynn
  • Members
  • 1 387 messages
I'm up for a modders toolset re-patch :D..

Whaddaya say Bioware? Little fix..you know...old script...take out..no biggie..put back new script if any. Pretty please?

#24
DLAN_Immortality

DLAN_Immortality
  • Members
  • 481 messages
Bump. Come on, Bioware, where's your support for your loyal customers? :-)

#25
DLAN_Immortality

DLAN_Immortality
  • Members
  • 481 messages
Bump. Bioware, where are you? :-)