Community Forums > Voobly Support and Game Complaints Support > Client and Website related Problems and Questions > Star Wars Galactic Battlegrounds Expanding Fronts support
4 User(s) are reading this topic (in the past 30 minutes)
0 members, 4 guests
0 members, 4 guests
What's popular right now:
AoKTS updates (69 users)
1.6 reward campaing (55 users)
Word Association (48 users)
CBA PathBlood 1.8.0 (42 users)
New Voobly Client 2.7 (30 users)
Photos of Voobly Players (21 users)
New CS EVENT (18 users)
Most active threads in past week:
Torneo 1v1 HUMAITA / HUMAITA 1... (31 posts)
🌟 Let's Restart Custom Scenar... (15 posts)
Error al lanzar la partida (4 posts)
game just closed (2 posts)
AOM Error "Unsupported Grap... (2 posts)
no record games anymore in voobl... (2 posts)
how can i download the game? (2 posts)
[You must login to view link]
Sadly, for the expansion to be useable on Voobly, some small adjustments are required that our coder (https://www.voobly.com/profile/view/123289067) cannot do on its own.
Would it be possible to get in touch, on whatever communications platform desired, so it can be discussed?
It would not take much, and it would be great to be able to play the mod on Voobly with all of its features instead of having to resort to other clients with inferior lobby systems and all that.
On behalf of the EF Dev team,
Regards
0x0046A920, 0x004A9411, 0x004BE147, 0x005F6757, 0x004290A8. Would it be possible to update the client to reflect these changes?
The two major problems I've spotted so far is
1. EF modified DRS load list which conflicts with the Voobly Data Mod interface which modifies it on its own.
2. Language INI string modifications do not seem to be supported for SWGB on Voobly mod framework side.
Perhaps there might be something else.
Have you tried using your mod center for custom DRS files?
EDIT: The mod framework seems to only let you replace existing DRS files, not add new ones / remove old ones.
Are you saying that, when you program a new graphic on AGE and load a file with that number into de drs folder, then it's not displaged in game?
efpatch use this widescreen code?
[You must login to view link]
did he resize slp interface into "data\\wide_p1.drs" or did use INTERFAC.drs?
I love and appreciate you
Which game is affected, SWGB or SWGB Clone Campaigns? Or do we have to create a third game, called SWGB Expanding Fronts?
Please also answer the questions raised by Katsuie:
efpatch use this widescreen code?
[You must login to view link]
did he resize slp interface into "data\\wide_p1.drs" or did use INTERFAC.drs?
why write injection in same sector than userpatch resulting in crashes and out of syncs elsewhere.?
you have abity to fix that, people who made those patch on voobly leave for some moth or for some of them will never come back.
if you want extention on voobly you need to fix it or make a choise compile patch without widescreen and use voobly widescreen.
However, Voobly widescreen can just as fine be used instead, however, it will need to be updated to support stretching new civs interface panels, and the bugs mentioned earlier fixed. I'll outline them again with more details:
0x0046A920 - erroneous shift of the recorded game interface
0x004A9411 - tile pathing property mask, not resolution (causes out of sync)
0x004BE147 - tile pathing property mask, not resolution (causes out of sync)
0x005F6757 - campaign scenario load, not resolution (causes crash when starting a campaign)
0x004290A8 - message id, not resolution
0x005068C0 - removes tech tree button handler (why has it been done at all? Is there some problem I'm not aware of?)
EDIT: I'll outline changes to DRS loading as well, so an optimal solution can be thought of:
Original SWGB:CC loads DRS files in this order: