Page 1 of 4

Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 1:43 pm
by Klonan

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 1:50 pm
by steinio
Why does the rail clock clear all segments on transition and not only this needed to be cleared?
There is plently room for optimisationalso as the transitions take ages.

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 1:58 pm
by Gergely
It looks like we get two new controllers in 0.17. Great!

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 2:03 pm
by Gergely
Huh... what happened to those rails? Is that part of the bug?

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 2:15 pm
by arrow in my gluteus
Gergely wrote:
Fri Dec 14, 2018 2:03 pm
Huh... what happened to those rails? Is that part of the bug?
I think they hide the rails on purpose with mods.

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 2:16 pm
by V453000
arrow in my gluteus wrote:
Fri Dec 14, 2018 2:15 pm
Gergely wrote:
Fri Dec 14, 2018 2:03 pm
Huh... what happened to those rails? Is that part of the bug?
I think they hide the rails on purpose with mods.
Yeah wheybags the savage made the other pieces invisible. :D

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 2:28 pm
by Philip017
i have never been a fan of cutscenes in video games, i would recommend they be optional (skip able, press ESC to skip) and any information they contain be available in other formats.

if i run into problems i usually use google and youtube.

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 2:48 pm
by mtreis86
Suggestion regarding the cut scenes:
If planning to zoom in, pan first, then zoom once on-scene
If planning to zoom out, zoom out first, then pan to the scene

I think this should make it smoother, but the only way to know is test

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 2:53 pm
by arrow in my gluteus
mtreis86 wrote:
Fri Dec 14, 2018 2:48 pm
Suggestion regarding the cut scenes:
If planning to zoom in, pan first, then zoom once on-scene
If planning to zoom out, zoom out first, then pan to the scene

I think this should make it smoother, but the only way to know is test
and when panning very far, zoom out first, even if you need to zoom in at the end.

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 3:19 pm
by nosports
That clock looks very cool……

I don’t know how difficult is to translate it to a Screen saver ?

Running Factorio as Screensavere seems somewhat very resourcefull…..
But on the other hand you need only an animation for every number 0-9 and then place it on the screen accordingly….

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 3:41 pm
by wheybags
steinio wrote:
Fri Dec 14, 2018 1:50 pm
Why does the rail clock clear all segments on transition and not only this needed to be cleared?
There is plently room for optimisationalso as the transitions take ages.
Because it's much easier that way.
Feel free to send a pr when 0.17 is out :v
nosports wrote:
Fri Dec 14, 2018 3:19 pm
I don’t know how difficult is to translate it to a Screen saver ?
Probably fairly hard. It's a multiplayer game, and windows screensavers iirc need to be compiled as some special kind of executable, which factorio.exe is not.
That said, a prerendered video might work.

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 3:53 pm
by mexmer
wheybags wrote:
Fri Dec 14, 2018 3:41 pm
steinio wrote:
Fri Dec 14, 2018 1:50 pm
Why does the rail clock clear all segments on transition and not only this needed to be cleared?
There is plently room for optimisationalso as the transitions take ages.
Because it's much easier that way.
Feel free to send a pr when 0.17 is out :v
nosports wrote:
Fri Dec 14, 2018 3:19 pm
I don’t know how difficult is to translate it to a Screen saver ?
Probably fairly hard. It's a multiplayer game, and windows screensavers iirc need to be compiled as some special kind of executable, which factorio.exe is not.
That said, a prerendered video might work.
record 24 hour cycle with obs, a pack it into scr? :D

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 4:45 pm
by nosports
mexmer wrote:
Fri Dec 14, 2018 3:53 pm
wheybags wrote:
Fri Dec 14, 2018 3:41 pm
steinio wrote:
Fri Dec 14, 2018 1:50 pm
Why does the rail clock clear all segments on transition and not only this needed to be cleared?
There is plently room for optimisationalso as the transitions take ages.
Because it's much easier that way.
Feel free to send a pr when 0.17 is out :v
nosports wrote:
Fri Dec 14, 2018 3:19 pm
I don’t know how difficult is to translate it to a Screen saver ?
Probably fairly hard. It's a multiplayer game, and windows screensavers iirc need to be compiled as some special kind of executable, which factorio.exe is not.
That said, a prerendered video might work.
record 24 hour cycle with obs, a pack it into scr? :D
in the end you need only the movies for every single number 0-9.
You need to place them the naccordingly

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 5:01 pm
by Nova
Cutscenes? Nice! I always liked making custom cutscenes in other games. Will help for the campaign, too. :)

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 5:15 pm
by hovissimo
arrow in my gluteus wrote:
Fri Dec 14, 2018 2:53 pm
mtreis86 wrote:
Fri Dec 14, 2018 2:48 pm
Suggestion regarding the cut scenes:
If planning to zoom in, pan first, then zoom once on-scene
If planning to zoom out, zoom out first, then pan to the scene

I think this should make it smoother, but the only way to know is test
and when panning very far, zoom out first, even if you need to zoom in at the end.


Registered just to contribute here. The "near ground" sliding camera movement in the FFF animation is very uncomfortable. I've never made a camera controller and I obviously don't know anything about Factorio's controllers, but I have some thoughts that could maybe help.

In my head I'm imaging the camera pointing down to the ground in 3-space. The initial and final positions could be described by x,y,z coordinates where the z coordinate would correspond to zoom level. The catenary curve between these two points should satisfy mtreis86's (and my) request and also look swank. I agree that a linear interpolation is dull. I think a parabolic arc would be nearly impossible to tune so that it looks good.

A possibly simple implementation of "arrow in my gluteus''s suggestion would be making the camera interpolation a sum of functions, and adding the ground-speed of the camera to the camera's z-position/height.

This is all probably obvious to you guys, but maybe I'm helping a little bit.

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 5:35 pm
by Jon8RFC
Rather than submit a second form and skew the results (I closed it as I realized I could edit my response), I wanted to give a recent example of proofreading the English for consistency, whichever way is chosen--localisation vs localization.

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 6:04 pm
by Nightinggale
NOOOO... please do not add uncontrollable camera movements and break the game with them. The problem is motion sickness. Moving the camera has a tendency to cause motion sickness in people prone to motion sickness. Moving the camera without user input makes this problem far worse. User controlled camera movements means the player expect the movement, meaning the problem is significantly reduced. On top of that if a certain kind of movement has a tendency to cause motion sickness for a certain player, that player can just avoid doing the camera movement in question. Cutscenes sounds like they could easily be the worst kind of camera movements as they are unexpected (sort of anyway), uncontrollable and unavoidable.

I fear Factorio might end up in the "can't play" category because of this and I really don't want it to end like that.

If you insist on implementing cutscenes, at least make them controllable with settings, like setting acceleration and max speed. Also make sure mods can't overwrite the user settings for those two settings. Sudden and fast movements are much worse than smooth movements when it comes to risk of motion sickness.
mtreis86 wrote:
Fri Dec 14, 2018 2:48 pm
Suggestion regarding the cut scenes:
If planning to zoom in, pan first, then zoom once on-scene
If planning to zoom out, zoom out first, then pan to the scene

I think this should make it smoother, but the only way to know is test
I second this. On top of likely looking better, zooming is less of an issue than scrolling when it comes to motion sickness.

Zoom out to a height where both origin and destination are visible and then zooming in again would give a sense of overview, which is great when the player wants to figure out where the camera is moved to. This can be combined with slow movements for scrolling, which will allow the scroll movement without feeling like a scroll. Besides if the scroll is done primarily while zoomed out, the scroll has less of an on screen distance to travel, making it much less of a scroll.

Still it would be nice to have all speeds for this user configurable, as in speed and acceleration for both scroll and zoom. Maybe configurable to not allow movement in more than one direction at once, meaning zoom out, scroll, zoom in.

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 6:36 pm
by Delzur
I wonder if there are players learning esperanto like me that would like to make a translation! (Beginner, but that would be a nice learning project)

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 6:53 pm
by manetje76
I can eventually help with the Dutch translation

Re: Friday Facts #273 - Cutscene controller & Localisation plan

Posted: Fri Dec 14, 2018 7:00 pm
by Lubricus
The result of the questionnaire will be skewed towards people who is reading English and the FFF.