• This is a reminder of 3 IMPORTANT RULES:

    1- External self-promotion websites or apps are NOT allowed here, like Discord/Twitter/Patreon/etc.

    2- Do NOT post in other languages. English-only.

    3- Crack/Warez/Piracy talk is NOT allowed.

    Breaking any of the above rules will result in your messages being deleted and you will be banned upon repetition.

    Please, stop by this thread SoccerGaming Forum Rules And Guidelines and make sure you read and understand our policies.

    Thank you!

Stadiums by Gonzaga & BFL TEAM

gonzaga

Reserve Team
I didn't have them ready but here I tried one, tell me if this works:

Day


Night



Also, is this Allianz Arena compatible with the previous Allianz Arena release?
Meaning that if we have stadium_137 model, we can have stadium_137_textures_2006 for WC06, stadium_137_textures_2020 for EU20, stadium_137_textures_0 for all other games.
Thanks! No, this model is to be used separately. The model I released earlier is the same, but I took this Wizard's modified EURO version and I'm not sure if I edited the same parts as the previous one. I recommend to use the EURO versions separately.
 

Vndrew

Youth Team
Arena Nationala, Bucharest, EURO 2020.
Hi, guys! Here is the second EURO 2020 stadium - Arena Nationala. I used my own version of the stadium for this one, but used @The Wizard euro textures. I couldn't find the font to make the host city adboard. @V.K, if you have the font I can make the adboards myself.
Allianz Arena is updated with the host city adboard. Re-download from it's original post.



very nice version of Arena Nationala. can you also share the clean, non-euros version of it, please?
 

V.K

Starting XI
I couldn't find the font to make the host city adboard. @V.K, if you have the font I can make the adboards myself.
Isn't it the same font you used to write "Bucharest Host City"?
Anyway, here is the one I used
 

Attachments

  • Euro 2020 PF BeauSans Pro.zip
    178.6 KB · Views: 83

Emanuel Lucas

Club Supporter
I'm having problems with two stadiums in my FIFA 14. Tottenham and Leicester stadiums are causing the game to go alone. I've edited with the correct ID's, regenerated and saved everything right. All other Gonzaga stadiums are working perfectly, but I can't solve the problem for these two. Could you give me some strength in this?
 

gonzaga

Reserve Team
@Gonzaga

How can I rotate a stadium?
It's very tricky work. You have to select all the parts that you want to be rotated in object mode press R and tipe 180 and press Enter.Do not select the PROPS group and the elements in it. Do not select the stad_groups too.
Guys I have injured my hand yesterday, so I can't do nothing right now. As soon as I heal it, I'll be back.
 

moldoioan

Club Supporter
It's very tricky work. You have to select all the parts that you want to be rotated in object mode press R and tipe 180 and press Enter.Do not select the PROPS group and the elements in it. Do not select the stad_groups too.
Guys I have injured my hand yesterday, so I can't do nothing right now. As soon as I heal it, I'll be back.
Take care of yourself and I hope you'll get better soon!!!
 

V.K

Starting XI
Thank you so much for St Petersburg!

It's awesome to see it, although with stadiums like this (as well as Allianz Arena and others) I can't help but feel puzzled as to how to properly arrange them in the context of multi-era patches like the famous Classic Patch.

For St. Petersburg it would be preferable if Zenit, Russia NT, WC 2018 and Euro 2020 could all be played there. But separate models mean there should be 2 cloned stadiums in the patch, which takes up another stadium ID and extends the stadium selection list.
For Allianz Arena I have so far arranged Bayern FC (with tournamentdressing corresponding to the UCL season) and WC 2006 within the same stadium ID (by assigning a new texture file as stadium_x_2006), but now the Euro 2020 version would require a separate ID although being close to identical in essence.

This is just my train of thought and not complaints, of course, just thinking of the optimal way to have multi-purpose stadiums.
Maybe you will one day do it, maybe I'll try, but the way I see it working the best is as follows:
1. an awesome stadium is created with full on custom dressing (let's say St Petersburg WC 2018)
2. tournament dressing feature is activated on top of such dressing (but in the case of WC 2018 a blank texture file is created as tournamentdressing_SPb_2018)
3. that custom tournament dressing can be changed to other versions (Euro 2020 or Zenit) by creating new stadium_SPb_2020 and stadium_SPb_Zenit files respectively
4. since tournamentdressing feature is activated and it overrides the custom dressing, when Zenit 2017-18 plays at the stadium the correct tournamentdressing_x_ucl1718 is loaded, and when Zenit 2020-21 plays at it the correct tournamentdressing_x_ucl2021 is shown
5. optionally, a generic version can be created for all kinds of friendlies and other tournaments (like Confed Cup 2017) where tournamentdressing would override the grey walls

With this system we can have one stadium with single stadiumid but at the same time a whole variety of dressing versions covering all kinds of possible scenarios either by custom stadium_x_texture + blank stadiumdressing file or by an actual stadiumdressing.

This would work perfectly for multi-use stadiums such as Wembley, Allianz Arena. St Petersburg etc
 

gonzaga

Reserve Team
Thank you so much for St Petersburg!

It's awesome to see it, although with stadiums like this (as well as Allianz Arena and others) I can't help but feel puzzled as to how to properly arrange them in the context of multi-era patches like the famous Classic Patch.

For St. Petersburg it would be preferable if Zenit, Russia NT, WC 2018 and Euro 2020 could all be played there. But separate models mean there should be 2 cloned stadiums in the patch, which takes up another stadium ID and extends the stadium selection list.
For Allianz Arena I have so far arranged Bayern FC (with tournamentdressing corresponding to the UCL season) and WC 2006 within the same stadium ID (by assigning a new texture file as stadium_x_2006), but now the Euro 2020 version would require a separate ID although being close to identical in essence.

This is just my train of thought and not complaints, of course, just thinking of the optimal way to have multi-purpose stadiums.
Maybe you will one day do it, maybe I'll try, but the way I see it working the best is as follows:
1. an awesome stadium is created with full on custom dressing (let's say St Petersburg WC 2018)
2. tournament dressing feature is activated on top of such dressing (but in the case of WC 2018 a blank texture file is created as tournamentdressing_SPb_2018)
3. that custom tournament dressing can be changed to other versions (Euro 2020 or Zenit) by creating new stadium_SPb_2020 and stadium_SPb_Zenit files respectively
4. since tournamentdressing feature is activated and it overrides the custom dressing, when Zenit 2017-18 plays at the stadium the correct tournamentdressing_x_ucl1718 is loaded, and when Zenit 2020-21 plays at it the correct tournamentdressing_x_ucl2021 is shown
5. optionally, a generic version can be created for all kinds of friendlies and other tournaments (like Confed Cup 2017) where tournamentdressing would override the grey walls

With this system we can have one stadium with single stadiumid but at the same time a whole variety of dressing versions covering all kinds of possible scenarios either by custom stadium_x_texture + blank stadiumdressing file or by an actual stadiumdressing.

This would work perfectly for multi-use stadiums such as Wembley, Allianz Arena. St Petersburg etc
As I understand right you want to have one model for all the tournaments and with different tournament dressing textures in the tournament folder? I'm not sure what you mean by "creating new stadium". You want to use the specificstadium function?
 


Top