• 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!

Stadium Server R App

What is your experience with the stadium server app?

  • I am using it with no problem

    Votes: 8 22.9%
  • I tried but failed to get it work

    Votes: 8 22.9%
  • It looks way too complcate for me

    Votes: 16 45.7%
  • I am using it but it is buggy

    Votes: 3 8.6%

  • Total voters
    35
Stadium Server R App v1.8for FIFA16 can be download here:


Here is a link toward my R libraries that you now must use to install properly the server for the first time:

Copy paste the folder 3.6 to "/Documents/R/win-library"



Contains:
- v1.8 AIO
- update from v1.7 to v1.8

IMPORTANT:
- Version of R newer than 3.6.3 are not supported



It is compatible with every version of the game.


All the required info for the installation and how to use the tool are in the Readme.pdf file.

Please report any problem you might come through.


List of changes:

UPDATE v1.1

- Correction of an error when you tried to load an external folder with stadium files in stadium server format (model.rx3, ect...)
- Extracted stadium files for the default game stadiums are now stored in a zip files somewhere on your disks (previously decompressed and installed in game/data/sceneassets folder). The App now ask you once where is located the zip file (possibility to change the path later), and momently extract only the required files from the zip if any.
- Because of the above change, the size of the App install has reduced from ~5GB to ~2GB (Software and libraries ~500MB + extracted stadium files in the zip ~1.5 GB ).

UPDATE v1.2:
Small corrections to avoid errors when you pressed inadvertently a and s at the wrong time. The tool used to try loading the wrong screenshot all over again. Now if you press RUN again after an error, you are good to go (thanks Iwanamzan for the inspiration).

UPDATE v1.3:
- Correction of a small error with the SEARCH function. When a team from the DB had no stadium assigned it could cause an error if that team was returned in the suggestions
- Users that already have a cl.ini before installing the App MUST add the line STADIUM_ID=177 before any "[]" otherwise the line would not be red which turns off the Stadium Server App.

UPDATE v1.4
- Fixed a bug with crowd files that where not properly loaded if you assigned a stadium ID when adding a stadium to the map file with the ADD button.
- Previously if the folder (or zip) containing your stadium files have a ui folder, the .big files were copied to your game folder. Even though it didn't have any impact on the experience with the game it would add messy files in your sceneassets/stadium folder.
Now files from the ui folder are ignored by the app.

UPDATE v1.5
- Fixed a bug with glare files. Previously if the files you provided had either the lnx or the rx3 type but not the other type of file the server was assuming you had the both types and it would not look into your game folder or the stad_source.zip to collect the files, resulting in an error message telling you that glare files were missing. This is now fixed.
- The App now use the country column first then the comment column of your map_stadium.txt to sort and display the stadium list. Previously only the country column was used. This makes easier to find your stadium when you want to manage them (ie:update them)
- You must now press the key "$" instead of the combo "a" and "s" to load your stadiums at the kickoffhub screen. With the previous set up sometime the order to load a stadium was sent when "a" or "s" were pressed separately, resulting in a stadium trying to be loaded at the wrong time.

UPDATE v1.6
- Improved the ability of the App to discriminate text from the taken screenshot
- The Browse function now immediately save the provided path where before closing the app and reopening it was necessary
- The manual (available in the AIO) now provide the link toward the last version of R (v3.6.3) compatible with the tool. R v4 is not compatible with the tool.
- The manual now provide the updated download link for the stad_source_folder containing all the default game stadium files which are mendatory for the app.
- The gWidgetstcltk library install problem has been fixed.

UPDATE v1.7
- Fixed problems with libraries that were removed from CRAN, if you had already installed the tool before you are not concerned
- Edited the instructions for the installation steps of the R libraries

UPDATE v1.8
- Improved the optical character recognition (OCR) process performance. There is now less chances that a random stadium is picked instead of the wanted one.



Video tutorials:
1) App installation

[

2) How to use the App


Weaknesses and Strengths of the App compared with CGFS
The App is not really relevant for people that can already use CGFS.
Here are the weakness and the strength of my App compared with CGFS:

Weaknesses:
- Not easy to install (I am happy to help anyone)
- Requires some free disks space available (~2GB including the stadium_source_folder that contains all the default game stadium files that needs to be available to the App).
- It is not a File Server, it is only a Stadium Server.
- It requires the user intervention before starting a game (press a and s on the match preview screen aka kickoffhub)
- Stadiums can't be assigned to tournaments IDs and tournament rounds IDs

Strengths:
- It is compatible with every version of the game.
- You can load any RevMod type of files that have a stadium ID with it (ie: specificgoalpost, ect...).
- The App can read stadium files stored in .zip compressed archive which in the end might result in a net gain of disk space (lost through install size - gain with compressed stadium folders= gain?).
- Any stadium file format is supported (FS or standard), if in standard format the stadium ID doesn't matter. For both format you can only add some files (ie textures) to files already installed in your game (ie: model, crowd, ect...).
- Teams which are linked in the DB to a stadium with an exterior camera will have the exterior camera.
- A function of the App allows loading any stadium already installed to your game or to the stadium map file simply by searching the Home team name or the stadium name. It can be used to load a particular stadium for a final ect...
- Stadiums can be added to the stadium map while the game is/is not started (it doesn't matter). You can add many stadium at the same time.


upload_2019-8-5_23-49-52.png
 
Last edited:

pe pe

Club Supporter
Just read the documentation - seem pretty complicated at a first glance, but I really appreciate the amount of work you put into this. I understand the reason for this is to play with modified exe, right? It is always good to have an alternative tool so thank you for sharing this.
 
Thank you very much @pe pe for the good words, it is always appreciated.
This is a project I started in April and it took me countless hours on my scarce gaming/modding time.

The very reason I made this Stadium Server R App is because I use the extended demo version of the game and there is no version of CGFS that works with it . While I added many stadium with CM16 to my game, I was always a bit frustrated about 1) The night bug for new IDs; 2) the time it takes to add new stadium with CM16; 3) and the impossibility to add new stadiums after I started a career.

Some could think this a Stadium Server for the pirate version of the game, but I personally don't support piracy. I own one legal copy of the game for PC but also one for the PS4. But, in my opinion the demo.exe of FIFA16 provide the best footy gameplay experience released to date. Also the retail game was very good too, until it was patched (to almost death for me, post 1.06 it is a disaster). It is so sad that we, as consumer, can't choose the version we prefer to play of a product we bought. I would buy a full price legal copy of fifa16 with the demo exe in a twinkling.
So yes, it works with every version, because it doesn't rely on memory addresses (which are different from one version to another) but on a OCR image processing of a screen shot taken by the user when the kickoffhub screen (after the kit selection screen) appears in game. The user needs to press the keys a and s together on their keyboard to take the screen shot. So unlike CGFS the user intervention is required to load the desired stadium.

As you mentioned, the installation process is not straightforward, but I hope my manual is good enough to allow anyone being able to install and start the App. Once installed, the uses is really easy. It is just a matter of double clicking a short cut (save of the very first session) and typing Stadium_Server() to the R console and then the App pops up.

The App is not really relevant for people that can already use CGFS.
Here are the weakness and the strength of my App compared with CGFS:

Weaknesses:
- Not easy to install
- Requires some free disks space available (~4GB including the stadium_source_folder that contains all the default game stadium files that needs to be available to the App).
- It is not a File Server, it is only a Stadium Server.
- It requires the user intervention before starting a game (press a and s on the match preview screen aka kickoffhub)
- Stadiums can't be assigned to tournaments IDs and tournament rounds IDs

Strengths:
- It is compatible with every version of the game.
- You can load any RevMod type of files that have a stadium ID with it (ie: specificgoalpost, ect...).
- The App can read stadium files stored in .zip compressed archive which in the end might result in a net gain of disk space (lost through install size - gain with compressed stadium folders= gain?).
- Any stadium file format is supported (FS or standard), if in standard format the stadium ID doesn't matter. For both format you can only add some files (ie textures) to files already installed in your game (ie: model, crowd, ect...).
- Teams which are linked in the DB to a stadium with an exterior camera will have the exterior camera.
- A function of the App allows loading any stadium already installed to your game or to the stadium map file simply by searching the Home team name or the stadium name. It can be used to load a particular stadium for a final ect...
- Stadiums can be added to the stadium map while the game is/is not started (it doesn't matter). You can add many stadium at the same time.
 
Last edited:
Hi, I'm having a problem with Python

He doesn't keep the window open, what I should do?


Hi! You should create a text file with a .py extension (ie: empty.py). Right click on it, select open with python and tick always use that application to open this type of file. It should fix your problem. Let me know if it doesn't
 
Last edited:

BrunoF07

Youth Team
Hi! You should create a text file with a .py extension (ie: empty.py). Right click on it, select open with python and tick always use that application to open this type of file. It should fix your problem. Let me know if it doesn't

Hi, thanks for the advise
It works now! =D
You made a great tool

I have one more question, I need to do the a+s every time I play, right?
 
Hi, thanks for the advise
It works now! =D
You made a great tool

I have one more question, I need to do the a+s every time I play, right?


Thanks for the good words!

Yes before every game at the match preview screen you must press a+s to load the stadium. Only if you play two times (or more) in a row in the same stadium you don't need to do it.

PS: I think you are the very first user of the tool. I am glad it works for you!
 

Fredhoer

Youth Team
I will use it too when i have finished my ongoing carrer and reinstall fifa, for the reasons i mentionned on evoweb (atmosphere and cameras related to the DB default assigned stadium of the team).

I just have a question. I have installed a mod which displays the real names of the stadiums (i think it was a db table, don't remember exactly). For exemple if i use the generic O Dromo for Real Sociedad, the name of the stadium in the pre game menu will be Anoeta. Will it make problems for the tool to recognize the stadium to load?
 
Not at all. Pretty much the opposite in fact. And you will see the name of the stadium correctly displayed.

The tool looks for two things from the screen shot you take by pressing a+s on the match preview screen, the stadium name and the home team name. If the stadium name displayed on the match preview screen doesn't match the stadium name linked to the home team in the db (stadiumassignement and teamstadiumlink) the stadium name gets the priority. This means that the stadium id in the db will be the reference used to load the stadium while otherwise it is the home team id that has the priority. So neutral games can happen on neutral stadiums.
 
Last edited:
v1.2 available to download in the opening post.

It contains a small correction to avoid errors when you pressed inadvertently a and s at the wrong time.

The tool used to try loading the wrong screenshot all over again. Now if you press RUN again after an error you are good to go (thanks Iwanamzan for the inspiration).
 
Last edited:
Sorry, again a small update to fix an error with the SEARCH function when a team without a stadium assigned in the DB (no entry in the teamstadiumlinks.txt) was returned in the propositions.

Also, for the users that already have a cl.ini, the lines to be added for the App have to be added before any "[ ]" or the line would be ignored by the game and thus the App would not be active.

The updates and fixes (v1.3) can be downloaded from the opening post.
 
Hi! Just a small update of the App to fix two small bugs:

- Fixed a bug with crowd files that where not properly loaded if you assigned a stadium ID when adding a stadium to the map file with the ADD button.
- Previously if the folder (or zip) containing your stadium files have a ui folder, the .big files were copied to your game folder. Even though it didn't have any impact on the experience with the game it would add messy files in your sceneassets/stadium folder.
Now files from the ui folder are ignored by the app.

The update can be downloaded on my PATATRON!
 
Last edited:
One short question: will the stadiums work if I play online?

Hi Nisoley!

I have no idea as I never played 16 online.
One way to quickly check if it would work is to try adding the following line to your cl.ini before any [ ] :
STADIUM_ID=177

177 is the "static" ID my app use but you can use 13 instead to "force" Anfield as the loaded stadium.
In game select any other stadium, if you get Anfield instead of the selected stadium then my app should work (probably loading the stadium for you but not for your friend or loading if you are the host... I am not sure how it works).

Let me know if it works and if you need help in the process.
 
Just a quick message to report a bug I am having sometime with the python script that takes screenshots after pressing the keys a and s.
Sometime (too often to my taste) the script takes a screen shot if you only press a or s which activate the loading stadium process at the wrong time.

It doesn't deserve a package update, but if you are like me annoyed about this, goes to your Stadium Server R App folder, open the python_script folder. And with a text editor open Screen_shot_shortcut_mss.py file.

Replace the line 7:
{keyboard.KeyCode(char='s'),keyboard.KeyCode(char='a')}

by

{keyboard.KeyCode(char='$')}

Save. Done!
Now press the key $ in game to take your screenshots and load the stadium.

I used $ but you can use the key of your choice. Just use one key because the key combination doesn't always work as intended.


PS: Also I have added a poll at the first page of the thread a month or so ago. Feel free to vote as for now it just look like only my friend and I voted. Not sure who this friend his, but I am glad the tool is working great for you! Cheers.
 
Last edited:
A small update to the Stadium Server to fix one bug and make two improvements:

- Fixed a bug with glare files. Previously if the files you provided had either the lnx or the rx3 type but not the other type of file the server was assuming you had the both types and it would not look into your game folder or the stad_source.zip to collect the files, resulting in an error message telling you that glare files were missing. This is now fixed.

- The App now use the country column first then the comment column of your map_stadium.txt to sort and display the stadium list. Previously only the country column was used. This makes easier to find your stadium when you want to manage them (ie:update them)

- You must now press the key "$" instead of the combo "a" and "s" to load your stadiums at the kickoffhub screen. With the previous set up sometime the order to load a stadium was sent when "a" or "s" were pressed separately, resulting in a stadium trying to be loaded at the wrong time.


The updated Stadium Server (AIO and update from v1.4 to v1.5) can be downloaded here: http://www.mediafire.com/file/tz1w3e1zvbz9dbp/Stadium_Server_Package_Pap_v1.5.rar/file
 


Top