You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After we are done with #98 I think it would be cool to have a table in that guide (or in another one) with a bit of information on how to shoot a specific unity game, similar to the UUU game table on framed or Frans docs page.
Here is a mock-up that Oliver made in an excel sheet:
When the guide FreeMoveInjector is done then we won't need info on the UUF version tested (maybe we could have a column with info on what was tested, if UUF (the old mod VTV made for getting the camera) or FreeMoveInjector. So the rows I would suggest would be:
Game Name
Type: Mono or il2cpp
Camera to Use: If I am not mistaken this would have the FoV value you will need to edit, besides other interesting/useful settings)
Camera to Disable: So the mod can control the camera without the game behavior intervening.
HUD to disable: the unity object that should be disabled in order to hide the hud.
Comments: Extra comments explaining how to make stuff work if needed (the unity objects to disable vignette or chromatic aberration for example), or if there is a cool trick this game has, like moving lights around.
Optional:
Unity version
Tricks and tips: If having the extra tips in the same cell as the comments for not-essential stuff is too much then maybe consider adding a column for them.
Regarding the comments and tricks, if there is a lot to unpack in a single cell in a table it might be worth considering branching a guide for that specific game.
The text was updated successfully, but these errors were encountered:
After we are done with #98 I think it would be cool to have a table in that guide (or in another one) with a bit of information on how to shoot a specific unity game, similar to the UUU game table on framed or Frans docs page.
Here is a mock-up that Oliver made in an excel sheet:

When the guide FreeMoveInjector is done then we won't need info on the UUF version tested (maybe we could have a column with info on what was tested, if UUF (the old mod VTV made for getting the camera) or FreeMoveInjector. So the rows I would suggest would be:
Optional:
Regarding the comments and tricks, if there is a lot to unpack in a single cell in a table it might be worth considering branching a guide for that specific game.
The text was updated successfully, but these errors were encountered: