-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
Sprint 1 Review #404
Comments
Weather Param |
Unsure if this is intended or not but with the S1 build there were no OPFOR spawning. No mods, didn't modify any mission files or parameters either. Fresh game, flew to nearest locations and no enemies. Edit: Apologies, I misunderstood. |
Please have a look at the content of the initial posting.
|
What is this?
This issue is used to collect all the bugs and problems that are found by the devs after a branch is merged or a sprint is finished.
As we will release a working iteration of the new framework after every sprint, everyone is invited to help with testing the sprint results.
The only thing to remember is that you should only report bugs in this issue, which are caused by the contents of this sprint (which are listed below). So it is vital to look at the content description to see what was actually added. Only by reading this you know what we've really intended to implement and defined as done.
I guess you understand that reporting things which weren't even planned to be part of the sprint won't help in any way.
Content of the sprint
Released sprint result
https://github.com/KillahPotatoes/KP-Liberation/releases/tag/v0.97S1
Bugs found so far
Spawn issue, when intro is disabled: Sometimes no respawn dialog and camera running forever.fixed in 669a882
Closing respawn dialog via ESC let you run around at the starting position.fixed in 92f18e2
Intro sometimes breaks with error about cursor pos. Might be caused by alt-tabbing during it (using borderless window). See logfixed in 669a882
Default value for weather param is 3fixed in 10d3387
KPLIB_fnc_core_spawnVehicle
can potentially get scheduled and this can cause bugs, we should consider wrapping it inisNil {};
to prevent possibility of thatThe text was updated successfully, but these errors were encountered: