Jump to content
Sports Interactive Community

a31632

Members
  • Content Count

    477
  • Joined

  • Last visited

4 Followers

About a31632

  • Rank
    Amateur

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. No problem at all, did you try just “height=“300” or higher/lower values? Did it not make any difference or did the details disappear? Unfortunately the coding was “autosize vertical” which means that there are no sections below it and it should be “spread out correctly” in the space available. Another alternative would be to reduce the size of the upper portion of the screen (where the scores and the stadium pictures are), that way you should have more space available at the bottom, but from your screenshot it looked like there is some unused space below the incidents (goals, yellow cards etc.) anyways. It would be involving a lot more coding to be changed too. Last thing you could try is to try it with changing the coding from: <record index="0" alignment="centre,centre_y" To for example: alignment=“top” or alignment=“top, extend” and see if that works with your resolution. I can’t test it for you I’m afraid and maybe it’s one of those things that can't be fixed as the resolution doesn’t allow it, but at least you tried. Glad the club screen worked out for you!
  2. The portion with the match events (goals scored, yellow cards etc.) is controlled by the files: "match incidents overview popup left2.xml" and "match incidents overview popup right2.xml" (one file is for home team, the other one for the away team), they are in the "panels/match" folder of the skin. in file ".....left2", navigate to line 63-73: <widget class="table" id="miit" layout="40,-1" row_spacing="-7" auto_size_rows="true" fixed_size_rows="false"> <list id="column_properties"> <record index="0" alignment="centre,centre_y" auto_size="vertical" /> <record index="1" alignment="left,centre_y" spec="control" colour="match text" /> </list> <list id="column_display_properties"> <record index="0" id="icon" left="4" top="4" bottom="4" /> <record index="1" id="text" top="4" bottom="4" /> </list> </widget> Very likely the highlighted section is causing the issue in your resolution as space is limited compared the 1920x1080 resolutions and the "auto size" command does not work good for your resolution. I can't test what happens with your resolution if you either change the value or delete the highlighted code. You might have to play around with that section (<record index="0" alignment="centre,centre_y" auto_size="vertical" />) a bit, if deleting or editing doesn't work you might have to add, for example, height="300" (or default_height=/minimum_height=) or a different value instead of the auto_size code). Usually I don't reply to requests for adjustments with higher/lower resolutions as my skin is made specifically for HD resolutions and has been tested to work fine with this resolution, but hope this helps you.
  3. Hi, the resolution you are using on your Mac is causing this, I’m away from home till Saturday because of work and will tell you which panels and which section of it you will need to edit upon my return. The skin is designed for HD resolutions, so using higher or lower resolutions can cause some screens or portion of screens to look different than usual. But of course everything can be adjusted with a bit of work.
  4. These questions have nothing to do with this thread. You would have to move it so it doesn’t impact this one. If your question is related to a skin, in this case OPZ, ask the question on the thread of the skin in question. Users who have the skin might know the answer you are looking for. Thanks
  5. I really wouldn’t know, I don’t use Andromeda skin and with me it works without problems with the suggested solution, sorry.
  6. I don't use the Andromeda skin so it could be different in that skin, with me I had to do the following: Open "header.xml" in "panels/generic" and find where the "titlebar code" is, usually it says something like: appearance="boxes/custom/interface/titlebar/paper" or a similar reference to the "paper" files (xml and png) that control the titlebar. Change this code from "paper" to for example "paper1". Next: go the the graphics folder where the titlebar graphics are (in my case "boxes/custom/interface/titlebar" and rename the paper.png and paper.xml files all to "paper1". Reload the skin and it should now work good.
  7. To solve this go to the file "scouting centre message card" in the "panels/widget" folder. Line 253-256 shows: <record> <integer id="get_property" value="SCpa" /> <integer id="set_property" value="clke" /> </record> Change these values to: <record> <integer id="get_property" value="SCma" /> <integer id="set_property" value="click_event" /> </record> While I was in the panel I also reduced the size of the confirmation button slightly, see screenshot below. If you like to reduce the size of the button go to line 245 in the same panel: <container height="50"> Change the value "50" to for example "30". To make the button less wide (which I think will look better in combination), go to line 249: <widget class="icon_button" id="ackn" auto_size="horizontal" auto_size_minimum_width="200" red_replacement="blue 400" icon="icons/16px/right" icon_alignment="centre" alignment="centre"> I changed the "200" to "100" and with both changes implemented it will look like below:
  8. I haven’t really played the game yet, I’m still playing FM 2018 until the last patch is out for this one, so I haven’t encountered the issue as I’m in the first season and none or almost no regens. I assume from what you are saying this only happens with regens? If so, I will need to recreate this situation so I can resolve it, the resolution should be simple, but I will need your save game so I can see what is causing this. Could you please upload your save game and send me a PM with the download link?
  9. As Jovovich and Steveyisatard both mentioned the skins match titlebar and related panels can conflict with the scoreboard. Jovovich mentioned he is not going to edit files for people’s individual skin or preference which makes perfect sense. These scoreboard codings are intended for use with the base skin only. So, you will have to either connect with the skin maker of the skin you are using and hope they will offer support (usually skin makers don’t get involved with personalizing or changing things in their skin if not bug related) or go through the coding as Steveyisatard suggested and figure out what is causing the issue with your particular skin and resolution.
  10. Yes, I think there are multiple. This code should be added to the file "sidebar menu table.xml" <!-- Primary Logo --> <widget class="picture" id="lgtF" scale_picture="true" keep_aspect_ratio="true" image_alignment="bottom"> <layout class="stick_to_sides_attachment" alignment="bottom" inset="130"/> <attachment class="test_setting_attachment" get_setting="show_badges" default_value="true" set_property="hidn"> <boolean id="value" value="false"/> </attachment> <!-- tells the picture to listen to the 'main picture' global property being set, and set its own file property from it --> <record id="object_property"> <integer id="get_property" value="mnpc" /> <integer id="set_property" value="file" /> </record> </widget> Inset="130" depends on how it will look with your skin, you might have to move it up or down (higher number for example "150" will move the logo up
  11. How to change default scoreboard open panels/scoreboard_selector/scoreboard.xml Example: <!-- 1 --> <container id="1scr" hidn="false"> <layout class="stick_to_sides_attachment" alignment="all" inset="0"/> <widget class="match_titlebar_panel" file="scoreboard_selector/match title bar score epl" height="75"> <layout class="stick_to_sides_attachment" alignment="top" inset="15"/> <layout class="stick_to_sides_attachment" alignment="left" inset="50"/> <record id="object_property" get_property="objt" set_property="objt"/> </widget> </container> <!-- 2 --> <container id="2scr" hidn="true"> <layout class="stick_to_sides_attachment" alignment="all" inset="0"/> <widget class="match_titlebar_panel" file="scoreboard_selector/match title bar score ligue1" height="40"> <layout class="stick_to_sides_attachment" alignment="top" inset="20"/> <layout class="stick_to_sides_attachment" alignment="left" inset="30"/> <record id="object_property" get_property="objt" set_property="objt"/> </widget> </container> <!-- 3 --> <container id="3scr" hidn="true"> <layout class="stick_to_sides_attachment" alignment="all" inset="0"/> <widget class="match_titlebar_panel" file="scoreboard_selector/match title bar score bundesliga" height="40"> <layout class="stick_to_sides_attachment" alignment="top" inset="20"/> <layout class="stick_to_sides_attachment" alignment="left" inset="30"/> <record id="object_property" get_property="objt" set_property="objt"/> </widget> </container> <!-- 4 --> <container id="4scr" hidn="true"> <layout class="stick_to_sides_attachment" alignment="all" inset="0"/> <widget class="match_titlebar_panel" file="scoreboard_selector/match title bar score seriea" height="52"> <layout class="stick_to_sides_attachment" alignment="top" inset="20"/> <layout class="stick_to_sides_attachment" alignment="left" inset="30"/> <record id="object_property" get_property="objt" set_property="objt"/> </widget> </container> <!-- 5 --> <container id="5scr" hidn="true"> <layout class="stick_to_sides_attachment" alignment="all" inset="0"/> <widget class="match_titlebar_panel" file="scoreboard_selector/match title bar score laliga" height="50"> <layout class="stick_to_sides_attachment" alignment="top" inset="20"/> <layout class="stick_to_sides_attachment" alignment="left" inset="30"/> <record id="object_property" get_property="objt" set_property="objt"/> </widget> </container> <!-- 6 --> <container id="6scr" hidn="true"> <layout class="stick_to_sides_attachment" alignment="all" inset="0"/> <widget class="match_titlebar_panel" file="scoreboard_selector/match title bar score champ" height="50"> <layout class="stick_to_sides_attachment" alignment="top" inset="20"/> <layout class="stick_to_sides_attachment" alignment="left" inset="30"/> <record id="object_property" get_property="objt" set_property="objt"/> </widget> </container> <!-- 7 --> <container id="7scr" hidn="true"> <layout class="stick_to_sides_attachment" alignment="all" inset="0"/> <widget class="match_titlebar_panel" file="scoreboard_selector/match title bar score europa" height="48"> <layout class="stick_to_sides_attachment" alignment="top" inset="20"/> <layout class="stick_to_sides_attachment" alignment="left" inset="30"/> <record id="object_property" get_property="objt" set_property="objt"/> </widget> </container> set hidn=“false” what you want to keep as default scoreboard. set hidn=“true” for the rest.
  12. It wasn't really that much work, it was a lot more work and more coding to get the "old" tactics screens during a match back the way it was in FM 2018. Instead of 2 screens (one with a pitch and one having the team squad on it, now it's standard only one screen in FM2019). I preferred the FM 2018 setup with a bigger pitch and a tabbed container where you can select either the pitch or team squad.
  13. After finishing up my skin I decided to have a look at the tactics screen as I never really liked the fact that the layout had changed from FM 2018. I'm not really sure why it got done, In the old days you used to have "left sided" and "right sided" skin versions, as I'm right handed myself I decided to change the tactics screen back to make it look similar to last years' version. See below screenshot. I'm actually quite surprised that nobody released this in a skin so far, maybe I'm just the only one out there who thinks it looked nicer before.
×
×
  • Create New...