hmmmmmmm well from the looks of it, maybe that resolution is not a good one haha, ofc i set a random res and then drag the game window to a custom size
i do know full screen works
Printable View
hmmmmmmm well from the looks of it, maybe that resolution is not a good one haha, ofc i set a random res and then drag the game window to a custom size
i do know full screen works
If my client get any resolution higher then 1024x768, windowed or full screen, my map gets like that... Even I perform a custom size by dragging my game screen ;(Quote:
Originally Posted by HyperSin
https://i.imgur.com/o4wEWIK.png
https://i.imgur.com/YvkXt7d.png
Official perfect world had a easy solution to this. Back then the black boarders who offer the constraint of the main map image and player arrow tracking function did not exist in code and in a later version they were added. You would have to use d_uidebug 1 ingame and find the elementclient commands or function linkers these interface elements use. An edit like this is not for someone with lack of assembly or PW knowledge and would most likely be rather hard if there was not a way to enable such code in configs.pck. You can check interfaces.pck and configs.pck first but most likely it is some code you would have to replicate from later versions into your older one.
I Don't think I got, but I was searching for something in configs.pck like you say, and I found a thing to keep tracked...Quote:
Originally Posted by jv90
File: configs.pck
path: /configs/autofamilyconfigs/autoscene.cfg
I found the map basic settings, that is:
[World]num_block_row = 8
num_block_col = 8
world_width = 1024.0
world_length = 1024.0
block_size = 128.0
Was we all can see, this is references to world's map grid, that are made of a file from 1024x1024, as we can see in any map.dds file in surfaces.pck.
And as we know too, the grid is made by 8x8 squares..
I know this file means nothing to help us in this problem, but, maybe if we can only hook something to keeps checking map size versus resolution, this may fix, as you comment.
Example (fictive):
If (client_resolution > 1024 &&
client_resolution > 768 ) then
world_width = client_resolution world_length = client_resolution
// world_border_fulfill()
end
OF COURSE this is not a real algorithm, it's only to you guys to understand A LITTLE :X
I would start by looking for interface hook names in elementclient from WorldMap.xml in interfaces.pck then seeing how they function in elementclient 1.3.6 vs elementclient 1.5.1+ or maybe even compare XML file of each to see which feature was added to the XML and how it was implemented.
No clues yet...Quote:
Originally Posted by jv90
I try to look up into interfaces but don't know where I can find it...
Jv90, may you please upload 1.5.1 files to me, I'll gonna try to compare with 1.3.6 files to find it
Unfortunately I lost the server files and about this reason, I have to start all again, I think I was close to fix this problem, but my HDD burned. Well, I'm here to ask help for you guys, 1.3.6 lovers.
i have the same problem, someone knows how to fix it?
Yeah use higher version server files