Jump to content

Ascension and Yaga-Shura


Recommended Posts

I believe the size bonuses granted to halflings, dwarves, and gnomes conflicts with Ascension's Tougher Yaga-Shura. I got a 'parsing error' at lines 1-6, or some similar error to that effect. I'm not sure if there is anything you can do about it but I just wanted to throw it out there.

Link to comment

Ascension installs okay for me on top of Fixpack + OBC.

 

Can you open up your ascension.debug from your BG2 directory with a text editor and paste the few last lines (above WeiDU timings) here? Posting the whole thing if you're not sure is ok, but it'll be too large for a single post.

 

Ascension mostly overwrites rather than patches, so there may not be much we can do - but we'll look :laugh:

 

/edit

 

If you're using a version of the Fixpack earlier than v6, you'll want to uninstall that OBC component entirely (or upgrade to the latest version). There was a problem with the Mac port in earlier versions.

Link to comment

But nothing that should cause a parsing error or otherwise cause Yaga-Shura to complain (this component shouldn't touch him at all -- it only affects generic fire giants and the three ettins that are in the game).

 

If you're getting a parsing error, it's likely a version mismatch between whatever TP2 WeiDU is trying to parse and whatever version of WeiDU is currently running (only thing I can think of, at least)?

Link to comment

Well I'm not sure what it is now. On occasion I get errors caused by the Fix Pack. Here's an example.

 

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2] PARSE ERROR at line 4 column 1-6
Near Text: README
syntax error

[BG2FIXPACK/SETUP-BG2FIXPACK.TP2]  ERROR at line 4 column 1-6
Near Text: README
Parsing.Parse_error
ERROR: parsing [BG2FIXPACK/SETUP-BG2FIXPACK.TP2]: Parsing.Parse_error
[dialog.tlk] created, 74512 string entries

 

Not exactly sure what's causing the issue. This is when I tried to install the Tougher Yaga-Shura component of Ascension. Sometimes it shows up for Unfinished Business too. Hope this helps.

 

And sorry about the length. I don't know how to put this in a scrollable box.

 

Oh, and here's the debug file.

Link to comment

Yeah.

 

Best bet for a quick fix is to replace the setup-ascension with a renamed copy of setup-bg2fixpack - back compatibility is fine up to 206, but ascension era WeiDU isn't going to be handling any stack uninstall reinstall options with anything written in the last three years or so.

 

The first six lines of the ascension .tp2 are just //// anyway :laugh:

Link to comment

Nythrun can give you the exact instructions for replacing the Ascension exe with the fixpack's under Windows.

 

The errors you're seeing are actually WeiDU errors - the fixpack is using commands that weren't available with older versions of WeiDU, so any time an older version of WeiDU tries to parse the fixpack TP2, it'll fail when it gets to one of the unsupported commands (in this case, README is a command added to WeiDU well after the last Ascension update).

 

WeiDU is supposed to automatically update other instances of itself (all Setup-*.exe files in the current game directory), but it looks like it's pretty useless with the number of times issues like this crop up.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...