Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Self-adjusting AI/GS max opcodes #7459

Closed

Conversation

SamuXarick
Copy link
Contributor

This is an experimentation so far. Goal is to permit playable framerate with many AIs running. Based on the performance data measured, the value of max opcodes is increased / decrease every GameLoop.

@PeterN
Copy link
Member

PeterN commented Apr 2, 2019

Regression testing is never going to work with this.

@SamuXarick
Copy link
Contributor Author

SamuXarick commented Apr 2, 2019

TODO: deprecate script_max_opcode_till_suspend (remove from savegames, etc...)
BTW, Regression should have failed. Must check why it didn't.

@TrueBrain TrueBrain added the wip Work in progress. Feature branch that will require feedback during the development process label Apr 2, 2019
@TrueBrain
Copy link
Member

Although I appreciate experimenting, I do not think this has a place in OpenTTD. Patches like this are solving the wrong problem, in my opinion. It only means that people on low-end computers have a lesser experience than those on a high-end. It also means that games are completely undeterministic now as soon as an AI is involved. I can only see more bug tickets happening because of this.

Of course, you are more than welcome to experiment further with this, and see where it ends up. But I do not think it should be an active Pull Request, where we can see every change you make to this while experimenting :)

@TrueBrain TrueBrain closed this Apr 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wip Work in progress. Feature branch that will require feedback during the development process
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants