Backdrop visual list #85
Comments
|
Any custom entries to RESDATA must be at the top, and the original 38 lines
below that. If the custom entry matches an existing GroupID, then it gets
overridden. Not something I've looked into, but I would bet that XWA
doesn't load an image if the ID is already occupied, so whatever's first
wins.
For the hook, it's looking for [mission]_Resdata.txt first, then
[mission].ini, and if it's the INI it's looking for the"[Resdata]"
section. The entries are relative to the base directory, so for example
SuperBackdrops usage has "resdata\planet2.dat". Then same as just using
RESDATA, it's looking for the DAT's GroupID and replacing it if found.
What does your RESDATA.txt and INI look like?
--
…On Mon, Aug 7, 2023 at 6:09 PM ual002 ***@***.***> wrote:
It appears that no matter what I do to the resdata txt file, the backdrop
visual list still shows the same set of backdrops, additionally, adding a
backdrop replacer via INI in the hook assignemnt tool also appears to have
no effect on the visual list.
—
Reply to this email directly, view it on GitHub
<#85>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHO5ERWL6RHICV4MLPGZY3XUFYUBANCNFSM6AAAAAA3HULAUU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Its the TFTC 1.3.3 standard, but I've messed with it since. Let me see if I can re-upload the mod's file in original state. All I was saying is that it might be prudent to override YOGME reading any particular dat from the resdata file when a mission ini specifies something else, negating the need to have any particular resdata formatting or order. All of the TFTC missions include a mission INI and I think all of them specify at lease a different planet.dat. Its its like pulling teeth getting changes to certain files to stick with all of us doing edits to the mod. So the backdrop picker could load defaults according to the resdata file, and if is formatted weird, as in the case of TFTC, use the hook assignment tool and overwrite it with an INI, both for the mission in-game and yogme itself. A good example use of this would be, even if TFTC formatted the resdata file properly, maybe I'd make a mission addon pack for the tour MP hook, in that case I might make my own UAL002planet.dat, distribute it with the mission pack, and it would be easier for me to edit my missions with the right backdrops if YOGME just read my mission.ini pointing to UAL002planet.dat |
|
It does though. The INI is loaded last, and YOGEME will override what it
has.
1) Load defaults
2) Override with extra RESDATA lines
3) If the hook is installed, override with INI.
Sounds like it doesn't think you have the hook installed. If you've got
multiple installs of XWA, make sure that the one you're pointing at (via
Options dialog) has hook_backdrops.dll present in the base directory,
that's what YOGEME is looking for to determine if the backdrop dialog is
launched using the hook or not.
--
…On Tue, Aug 8, 2023 at 9:56 AM ual002 ***@***.***> wrote:
Its the TFTC 1.3.3 standard, but I've messed with it since. Let me see if
I can re-upload the mod's file in original state.
All I was saying is that it might be prudent to override YOGME reading any
particular dat from the resdata file when a mission ini specifies something
else, negating the need to have any particular resdata formatting or order.
All of the TFTC missions include a mission INI and I think all of them
specify at lease a different planet.dat. Its its like pulling teeth getting
changes to certain files to stick with all of us doing edits to the mod. So
the backdrop picker could load defaults according to the resdata file, and
if is formatted weird, as in the case of TFTC, use the hook assignment tool
and overwrite it with an INI, both for the mission in-game and yogme itself
RESDATA.TXT
<https://github.com/MikeG621/YOGEME/files/12292682/RESDATA.TXT>
—
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHO5EU67AVETI4PB2WI4CLXUJHRVANCNFSM6AAAAAA3HULAUU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
yeah that dll is present |
|
I'm going to do a debug build with a couple message boxes to show some
debug info, since I need to see what it's doing on your end. Should have
that ready tomorrow.
--
…On Tue, Aug 8, 2023 at 4:40 PM ual002 ***@***.***> wrote:
yeah that dll is present
—
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHO5EWUI4ZSMN7BAWVLYZ3XUKW45ANCNFSM6AAAAAA3HULAUU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
ill be on standby |
|
Redoing, original attachment didn't work. Zip of the whole debug build. Okay, so this will have two message boxes. First one is right when you click the backdrops button, lets you know where YOGEME is looking and if it detects the hook. Second one lists the details of the load. |
|
Still appears to load the default images @ 512 x 512 in the editor, but thanks to the mission.ini the larger tftc backdrops are loaded in the mission as before.
|
|
Well the "default" 512x512 images are really the upsized ones from planet2
that XWAU rolled into the original filenames, since stock images are
256x256 max. So depending what you're loading (say planet2) then the
images are one and the same.
What's the full contents of the INI? YOGEME knows the hook exists, but
that says it's not seeing anything in the [Resdata] section, or that the
filename it's looking for doesn't exist. I think I can see a way for it to
skip through, depending on how the INI's done.
--
…On Wed, Aug 9, 2023 at 9:08 PM ual002 ***@***.***> wrote:
Still appears to load the default images @ 512 x 512 in the editor, but
thanks to the mission.ini the larger tftc backdrops are loaded in the
mission as before.
[image: image]
<https://user-images.githubusercontent.com/7959255/259596803-51b856d8-9804-490f-bf0e-3f99bfffae4e.png>
[image: image]
<https://user-images.githubusercontent.com/7959255/259596912-467d2621-6e5d-42d0-936d-6ed52668166c.png>
[image: image]
<https://user-images.githubusercontent.com/7959255/259597238-69c17679-cd3a-4f4c-93e7-a3145bd482cb.png>
—
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHO5ETLIUSRPHFVXUKVZETXUQ7CTANCNFSM6AAAAAA3HULAUU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
INI was just what the wizard was adding. ;8B84M9B.ini [Resdata] This is stuff in the Combat folder though, not the mission folder. |
|
Well that's the problem then, it's looking for the INI in the \Missions
directory. I can make the change so it follows whichever directory it's
sitting in. The BackdropDialog handles it a little differently since it
normally has no need to know what the mission is.
YOGEME wasn't designed with \COMBAT in mind, as hardly anyone ever messed
with those due to the difficulties with co-op prior to the existence of the
hooks. Similar to the WAV issue, you're likely the first person in the 15
years since I started it to make a serious effort with multiplayer, so
you're likely to keep running into little things like this.
--
…On Thu, Aug 10, 2023 at 1:29 AM ual002 ***@***.***> wrote:
INI was just what the wizard was adding.
;8B84M9B.ini
[Resdata]
Resdata\PlanetTFTC.dat
This is stuff in the Combat folder though, not the mission folder.
—
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHO5EV52FEEVKUFFBMXPHLXUR5U3ANCNFSM6AAAAAA3HULAUU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
And thats fine, I'll try and keep that in mind and if running into walls like that, take the time to test things in a more typical SP situation to see if I have similar results to help you get to the solution quicker. The tour MP hook justagai made and Jeremy took over is truely very powerful, and if you can manage to wrangle enough people in the same place for coop stuff its a lot of fun, but theres plenty of little polish bugs to sort out in the hook itself anyway. Sometimes I make single missions just for my own enjoyment because I get the benefit of having a mission selector, rather than the linear progression of the campaign room. |
It appears that no matter what I do to the resdata txt file, the backdrop visual list still shows the same set of backdrops, additionally, adding a backdrop replacer via INI in the hook assignment tool also appears to have no effect on the visual list (but it does affect the dat for actual in game purposes). Unless I'm missing something, I do think the hook assignment tool, backdrop replacer section is a good way to not only set the dat file for the mission, but hard set the visual catalogue of available backdrops in YOGME rather than relying on resdata text file edits.
The text was updated successfully, but these errors were encountered: