laneystain
-
Posts
47 -
Joined
-
Last visited
Content Type
Forums
Articles
FAQs
Online Manual
Support: Blocks
Support: Games
Bug Tracker
SIGames Manual (beta)
Profiles
Posts posted by laneystain
-
-
12 hours ago, autohoratio said:
I suspect this is because of how the game views "Primary" kit colours. It views the "Primary" colour of the Wolves home kit as Black, and the "Primary" colour of West Brom's home kit as Navy Blue, therefore judges it to clash. West Brom's third kit is judged to be either primarily Red or Yellow, therefore incorrectly no clash.
This has been an issue for years unfortunately.This could well be the case but it should be something relatively simple to fix in the Editor. It's not possible for us to edit the Kit Selection area unfortunately.
It looks an absolute mess on the 3D match engine, playing away with Wolves isn't too much of an issue on 2D as the away kit uses the sky blue as primary colour.
0 -
This has been an issue since release and I can see from the Editor following the Winter Update that it's still not been resolved. Wolves clash with a couple of other clubs as well, but most notably West Brom where the home and away kits are being used incorrectly.
FM have told me this is a known issue but at least two updates have been released since it was raised by someone else and the issue is still there.
If this is the wrong thread can someone point me in the direction of where it needs to be to get it sorted!
0 -
On 08/01/2021 at 10:13, laneystain said:
No idea if this is the right thread but there's a kit clash between Wolves and West Brom both home and away (screenshot attached for reference). I understand this was raised previously but is still an issue. It's impossible to change via the pre-game Editor in the "kit selection" screen.
West Brom should play in their home kit at Molineux and Wolves should be fine to play in their home kit at the Hawthorns.
Just checked on the Editor following yesterday's Winter update - this is still an issue and hasn't been picked up.
1 -
This still hasn't been resolved in the Winter update. Surely it's not difficult to sort and I've been told FM are aware of the issue.
0 -
On 06/02/2021 at 21:37, Welshace said:
Just watched a full scout package on this guy in real life .. and he looks decent in game too thankfully... might be worth a punt...
That will please the Wolves board when I need to sign Portuguese players!
1 -
No idea if this is the right thread but there's a kit clash between Wolves and West Brom both home and away (screenshot attached for reference). I understand this was raised previously but is still an issue. It's impossible to change via the pre-game Editor in the "kit selection" screen.
West Brom should play in their home kit at Molineux and Wolves should be fine to play in their home kit at the Hawthorns.
0 -
@Valeria GraffI've also had similar issues with my Barcelona side in some La Liga games.
Also, kit issues/clashes between Wolves and West Brom that need correcting. I understand these were raised on the Beta bugs forum but still remain. The kit selection for both teams appear incorrect - West Brom play in their third kit when away (clashes with the gold/black) and Wolves play in their away kit when away (clashes with West Brom's blue/white).
0 -
Don't think these are the only clubs where this is occurring. It's been raised previously (before the latest update) but hasn't been sorted.
Wolves are set to play in their home kit at Molineux, West Brom are set to play in their 3rd kit (yellow and red) - an obvious clash.
At the Hawthorns, West Brom play in their home shirt but Wolves are set to play in their blue/white away kit.
This is to do with the settings in the "Kit Selection" in the pre-game editor. Can it be looked into and corrected?
0 -
Not sure if anyone else is experiencing this and why it's not been picked up on previously...seems to have been an issue on my games since the BETA.
Every time an opposition player scores the pop up with their name at the bottom sticks there until another goal is scored, rather than disappearing after a couple of seconds.
0 -
You can only offer him a contract from 1st Jan if you're based outside of England. City were foolish enough to loan him to me at Barca for the season, I then offered him a contract in January and he joined for nothing in the summer. Beat off interest from Juve and Bayern as it was "part of his career plans" to return to Barca.
0 -
I'm only able to use 3 subs in La Liga, should this not be 5 as per the rules in real life until the end of this season? I'm sure the blog released in October stated that substitution rules would continue as they were in real life for season one then revert to "the old normal" as with transfer windows.
1 -
Willy Bolly (Wolves) - contract is set to run until 2021, which both the club and local press (Express & Star) have confirmed is incorrect. His contract in fact runs until 2023. The defender in fact signed a 5 year contract when joining permanently from Porto in July 2018, rather than a 3 year deal.
0 -
Man City, obviously requiring centre-back reinforcements, decided to re-sign Stefan Savic.
Liverpool have won a bidding war against Man Utd to sign Adnan Januzaj.
Man Utd have now turned their attentions to Jonathan dos Santos.
I also seem to be noticing a lot of mid-table Prem clubs (Bournemouth, Palace, West Ham etc) interested in loaning Old Firm players who've only recently joined. Your Ryan Kents of the world, for example. Might be because I've not loaded Scotland as a league.
Atlas Guadalajara have just signed Neil Taylor from Villa for £3m. Bizarre.
0
.PNG.a342edb77bf5bdf4bca293270a86084f.PNG)
.PNG.0a9520117280c779a6b96ccdc8c62ec8.PNG)
.PNG.50e23afa6e4207a458a764b0c02cedd5.PNG)
.PNG.9e72bd7cb0918943ebcddc26d480b8aa.PNG)
Kit Clashes on Match Engine
in Match Engine - Art, Animations, Facegen and Manager Man
Posted
This has been an issue since release and I can see from the Editor following the Winter Update that it's still not been resolved. Wolves clash with a couple of other clubs as well, but most notably West Brom where the home and away kits are being used incorrectly.
FM have told me this is a known issue but at least two updates have been released since it was raised by someone else and the issue is still there.