Closed GoogleCodeExporter closed 9 years ago
Redoing Information:
INFC is is an Info Connection. It allows a topic to share an INFO from another
Topic. This makes it simpler and easier to have topics that have the same
dialogue responses share INFOs instead of having duplicates. It also reduces
the size of the game assets by eliminating duplicate voice files. You cannot
create INFC through the GECK, only the game developers' tool kit can.
INFX are the Info Indexes for the Connection, but as of right now they seem to
have no pattern to their format. 90% of them start at 0 for the first
connection and go up incrementally for each INFC. Except in some cases I've
seen a single one with an index of 1, 3 and in one case -1. I believe that the
index is simply a handler for the game to organize the connections and they
most likely do start with 0, the aforementioned oddities are errors original to
the game. Further testing will need to be preformed though.
Original comment by harkness...@yahoo.com
on 22 Nov 2012 at 7:09
2 questions:
1) what game is it?
2) what should be done?
Original comment by zila...@gmail.com
on 27 Nov 2012 at 2:36
New Vegas.
The program says unknown for subrecord identification (INFC - Unknown). This is
just explaining what it is so the unknown can be replaced with a proper title.
Original comment by harkness...@yahoo.com
on 27 Nov 2012 at 3:19
Update:
INFX are supposed to start at 0 for the first INFC and increment by 1 for each
INFC on the topic.
So an error check can be called on an INFC and it's INFX to make sure it is
numbered correctly. First the check collects the number of INFC for the topic
and then check the first INFC for the 0 INFX and then move onto the next + 1.
Original comment by harkness...@yahoo.com
on 16 Dec 2012 at 5:21
I added them to FNV definitions, but without your proposed index error check.
Even FalloutNV.esm has a bunch of wrong INFC, so counting INFX is pointless.
Original comment by zila...@gmail.com
on 20 Dec 2012 at 6:06
Don't know what else can be done here, so closing.
Original comment by zila...@gmail.com
on 19 Mar 2013 at 7:55
Original issue reported on code.google.com by
harkness...@yahoo.com
on 22 Nov 2012 at 1:18