Updating Manual images and text to reflect changes made in recent versions of Blender #75511
Labels
No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#75511
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
At the moment some pages in the Blender manual show images from Blender 2.7X. I will attempt to go through as many pages as possible and update these images to match more recent versions of Blender. If I don't know how a feature works and as a result can't replicate the image, then I will make a note of it here and let someone else update it.
This is simply a quality of life feature. Many of these images still show settings available in later versions of Blender, but it may confuse some new users.
While searching for these images, I will also check to see if the pages that contains the images also contain outdated information like incorrect menu locations or old keyboard shortcuts and fix them where possible.
I will also submit this fix as a series of patches, breaking the patch up into the sections defined in the manual (Getting started, User interface, Editors, etc).
Projects Status:
Others (E.G. Addons): Outside of my knowledge.
Sections I haven't updated (Primarily due to a lack of knowledge on my part):
Added subscriber: @Alaska
If anyone is opposed to this patch, please say so. For example, the only con I can see with updating this information is that we will need to store separate images for the 2.79 manual and 2.8X manual. However, with the images taking up 150MB as of writing, I don't believe this to be an issue.
Manual needs images updated to Blender 2.8Xto Updating Manual images to 2.8XAdded subscriber: @Blendify
If you search all the manual files for
.. TODO2.8:you will find a lot of images that need update.I can give you commit access to the SVN repository so you can commit changes directly. This is a lot easier on me than working with patches.
@Blendify So I've made my first commit rBM6491. Just had some questions.
At the bottom of /interface/window_system/regions we have a todo "Hiding and showing the Header". What kind of images do we want here? Should headers-hide.png just be the arrow at the top of the window and headers-show.png be a mouse over the arrow? Or should headers-hide be the RMB menu and headers-show be an image with a mouse over the arrow then an image below it with the header back to normal?
In /interface/controls/nodes/introduction I've updated the icons for shader nodes, compositing nodes, and texture nodes, however they don't look that great on the site. What would you recommend we do about this?
I've also made some edits to the text to include changes made in 2.8X, however, I have not commited those yet as I would like your opinion on what to do with them? Should I commit them directly or should I send them to you as a patch for review.
@Blendify I've updated the text in the user interface section rBM6496.
I had a few things relating to this:
In /interface/window_system/regions is "Footer" still a thing? Should we remove it?
In /interface/window_system/tabs_panels I have removed the "horizontal scrolling" part of "Switching and cycling" section as I'm unable to find a horizon tab that follows this rule with the default keymap. Revert this change if there is a tab system that follows this rule.
/interface/window_system/tabs_panels I have removed the pin icon information as I'm unable to find a menu that has a pin icon visible by default.
In /interface/keymap/introduction and /interface/keymap/blender_default I have left the "TODO" sections as TODO. This project is to update images, keymaps, and menu locations to Blender 2.8X. If I'm unable to explain something, then I'll leave it as a TODO.
ln /interface/controls/nodes/groups the second paragraph doesn't make much sense (check below), but I don't really know how to reword it. Any suggestions?
I've also sent /.htaccess by accident. For some reason it keeps changing in my local edits and I don't know why. (I'm running Linux if that makes any difference)
I've also started work on the editors section: rBM6498. Once again I have questions about this.
In /editors/3Dview/navigate I removed this (see below).
I couldn't find the option "Object>Move objects out of Local View" and the "Remove from Local View" option is covered later on in this page which I believe replaces this menu. Revert this change if you need too.
In /editors/3Dview/toolbar/measure I was unable to get these shortcuts to work, should we remove them?
In /editors/3dview/properties/sidebar the end of this paragraph (see below) doesn't make sense, what would you recommend?
Changed status from 'Needs Triage' to: 'Confirmed'
If you look into the images folder the old images still exist. The updated image should convey that if you click and drag down the header it will be hidden.
The images look fine to me.
Commit directly, please.
The footer is used in the text editor, so the information is relevant.
This is still relevant please revert that.
Sounds good, it gets a bit complicated to combine things.
This more a UI issue, they should both be called nodegroups whether they are appended or reused within a blend file.
don't worry about it, there is something wrong with the SVN ignore. I will try to fix.
"Object>Move objects out of Local View" was renamed to "Remove from Local View" which can be found in
View --> Local View --> Remove from Local View.See blender/blender#72767
Try this:
@Blendify I've made those changes. rBM6501 rBM6504
I'll probably start work on the rest of the User interface section today or tomorrow.
Thanks for the help. This has also been bit of a fun project for me as I'm learning about new short cuts and small actions that I didn't know about before.
@Blendify
I've done a bit more on updating the "editors" section. rBM6507
Also had to make a correction for a mistakes: rBM6507
Once again I have a few questions and clarifications.
In "/manual/editors/uv/introduction.rst" I've added a description for UDMIN grid but it probably needs review by someone who knows more about UDIMs than me.
In "/editors/uv/navigating" it states the view menu has an option for "Display Other Objects". I'm unable to find this option in 2.8X and believe it's been removed due to multi-object editing. So I have removed this. Please correct me if I'm wrong. (There was a "TODO" labeled "Blender Internal Only?")
I have quickly brushed over "texture_node" section in /manual/editors/ as I can't seem to get it to work reliably. Just to list a few issues:
Has this been mostly discontinued with Blender Internal?
I did notice that while going through different pages for nodes that I kept finding "Properties - This node has no properties". Should I remove them when I start work on the compositing section or leave them in for consistency?
In /manual/editors/dope_sheet there is a TODO from 2.78. Are you able to notify the right person about this or offer something to fill it in?
I have left most of "/editors/dope_sheet" untouched as I haven't used the dope-sheet before and some of the stuff goes straight over my head. However, all the images appear up to date, so someone just needs to check over the keymaps and menus.
The same thing of my lack of knowledge will probably occur in many other areas of the manual, I will let you know what areas I have trouble with when I get round to them.
"/editors/graph_editor/fcurves/editing" has the operation "extend" marked as "Todo". Seems to have been missed during the 2.82 manual, are you able to notify the right person about this or offer something to fill it in?
I've started work on some of the TODO stuff in "/editors/graph_editor/fcurves/editing" but I'm unsure about some of them so someone else will have to fill them in or make suggestions.
I have left the editors Compositor, Video Sequence, and Movie clip unedited so far as it helps me keep a track of changes I make. (Compositor, video sequence, and movie are all in separate folders which is half the way I'm managing this project.)
I also haven't finished the "editors" section yet. But this is as far as as I can really go today.
rBM6510
Correct I would skip over it for now, these nodes will either be changed a lot in the near future or removed.
This is kind of an incomplete feature currently, it will likely be expanded in the future but for now I can write a brief text about it when I get a chance.
rBM6511
If you are unsure of a todo please leave it for someone else, it will get done eventually.
Shifted to most recent comment.
Added subscriber: @jamjchai
Hello Alaska,
I would like to find out more about how I may help you with this task. I am new to contributing but the first time I picked Blender up was 2.5/2.49ish.
I personally don't know much about committing work that others have done as I have only recently started contributing to the manual myself (started about two weeks ago). So you'll probably need to talk to @Blendify about it. However, if you do start work on it, here's some recommendations based on what I've done so far:
Stick to a section. I've broken this project up into parts based on the sections defined in the manual. User interface, Editors, etc. What you may find when working in these sections is that a link will take you to a different section. So, the "Editors>Compositor" is actually a link to "Compositing>Index". The "Compositing>index" page is in a different section to "Editors", so I've put that off to the side so I can work on it when I get to that part. This is simply so I don't repeat the same work.
Test everything. If you make a change to the manual, make sure you test it out on your local version before proceeding to the next page. I personally do this as I'm new to RST (the format the site is written in) and sometimes make formatting mistakes.
Commit once you've finished for the day. For example, I've broken the "Editors" section up into three main commits because I did the update over three separate days. This is simply to make sure you don't end up in a situation where you spend a few days working on something then commit it, over-writing some of the work that the lead developers have done. I believe the system has a way of working around this, but I'm not 100% sure as I haven't tested it.
Please send me a message (probably in this thread) if you're starting work on a section and when you make a commit. This is simply so both of us don't go over the same work.
Use the latest version of Blender. Everyday I start work on updating the manual, I download the latest nightly build of 2.83 (the version of the manual we're updating). I also have a version of 2.79 installed so I can check to see if a certain setting that I can't find is in 2.79 and work my way from there to help me find it in 2.83.
Now that's out of the way, onto what this project is and how you may be able to help.
The main goal of this project is to simply update the images in the Blender manual to reflect changes made in Blender 2.8X. However, I have since adapted it by also looking at the text to see if menus or keymaps are listed incorrectly or some other issue. This means, going through every page in the Blender manual and reading them checking for mistakes or things that need updating.
And anyone can do that. Open up the manual, make changes, and submit them to the developers for review. The issue is that any image changes you make (the most common change) will simply show up to the developers as "an image has been changed" and we won't be able to see the image that was changed or apply the change. This means the person that changes the images needs to make the change directly to the manual which means you need commit access which I am not in a position to give. You will need to talk to @Blendify or some other manual manager for this access.
However, if you did want to start out with some text stuff, you can do that. You can find a guide for everything you need to start editing the manual here: https://developer.blender.org/tag/documentation/
Make sure you read through every step.
Also, just a quick tip. Once you get to the build section, the process of making a local copy of the manual, you will have to open the manual either through a command or through opening the .html file. Once that's done, when you next use the "make" command to rebuild the manual to update the changes you've made, all you have to do is refresh the manual in your web-browser. No need to reopen the file or use the command to open it.
And because I don't know where else to put it, if you start to update the manual, try and make the new images roughly the same size (in pixels) as the current images. You can go bigger or smaller, just stick to generally the same size.
And lastly. If you don't know how to update a part of the manual or believe a large change should be made, such as a the reworking of the file browser page to match the complete overhaul in 2.82, skip it and make a note so we know it's not complete.
Also, I'm not a Blender developer. I'm just doing this project in my free time. I am also not 100% knowledgeable in Blender. As a result, many little things that I'm unsure about, and you're unsure about when updating the manual, should be passed onto someone more involved with the documentation and development of this stuff like @Blendify.
Thanks for the thorough explanation, I appreciate your time on this. I will contact Aaron as you suggest and I was looking for a good foothold to start contributing and images seemed hard to mess up while learning the process, I understand now how images may be a little more involved than I initially anticipated.
I have already studied documentation concerning formatting, how to use RST, built Blender and the docs, joined the mail group, etc .... I just haven't made an edit or created a diff and have yet to contact anybody in the community. So I guess I will find my edits next.
I have been using Blender for modeling for some time now and figured working on the manual would be a great way to dig deeper to use features I may not have used before. I wouldn't have as much time to spend as you in this endeavor as I have a full time job as a Solidworks Drafter and I am taking courses toward a second degree in computer science (my first degree was in fine art). My current class I am taking is in open source development and my contributions here can apply to my grade, so I am motivated to help. I don't know how much time I will be able to devote going forward after this but I do want to continue contributing, Blender in part motivated me to pursue software engineering, and I have a capstone project coming up which I am hoping to incorporate Blender into also.
Thanks again for your advice.
@Blendify I've made another patch and once again have questions:
Now onto questions I had while making changes. rBM6540
I have left NLA mostly untouched as once again it goes over my head.
In the text editor, should "Format>Indent" (from the header) have a shortcut tool tip in Blender. The shortcut is in the manual but not in Blender.
Same question also applies for the python console under "Console>Indent". However Autocomplete has the same shortcut in both these cases.
In the info editor in Blender (Not the manual), should we still have the "Toggle selection" option under the "info" menu in the header. Seems to do the same as select all and deselect all?
In "editors/outliner" it says
I was unable to reproduce this last part "Shift to add/remove from the edit mode". Is this a bug?
The text in /editors/file_browser needs quite a bit of reworking. I've updated the image and will leave the rest to someone else as I'm unsure how to word everything.
In "/editors/preferences/navigation" it says:
However this option is not made available when you select "Fly" as your view navigation. Is this a bug or incorrect documentation.
In "/editors/preferences/system" I've added TODOs for disk cache
In "/editors/preferences/system" I have removed the parts that said "The available options are:..." On the basis of this in the writing style guide:
Correct me if I am wrong in doing this.
In "/editors/preferences/save_load" I've updated the two images there. However the second image doesn't fit properly in my personal opinion. Should I remove it?
In "/editors/preferences/file_paths" it describes a "Scripts" section that I've been unable to find in Blender (2.82 and 2.83). Should I remove this?
@Blendify I've made another update for the manual and once again have questions. rBM6545
Also may need a bit of rewording, I've just removed the stuff that doesn't apply to Blender 2.8X.
I've skipped over "/scene_layout/object/editing/relations" as it just went over my head. There are no images on this page so only the text needs to be checked.
"/scene_layout/object/properties/introduction" is just a "TODO". Are you able to notify someone about this as it's been like this since the 2.80 manual.
In "/scene_layout/collections/collections" it describes the use of a keyboard shortcut "Ctrl-G" to create a new collection. This collection is created but not added to the current scene. Is this a bug or is it working as intended? If it's working as intended, tell me and I'll update the manual to signify this.
The same page also describes a keyboard shortcut "Remove from All Unlinked Collections Shift-Ctrl-Alt-G" which just seems to remove the selected objects from all collections rather than do what the manual describes (see below). Is this a bug?
This doesn't seem to work for mesh objects. I remember talking to Brecht about this and he said it should stay in Blender for things like images, but I don't understand why it's still in Blender for mesh objects. Am I missing something?
But I don't know what to do to fix it.
I think this is because tab is shared between the autocomplete function (when you have a python file opened), I think in this case it is okay to reference in the manual and not in Blender
I am a bit unsure what you are talking about, I am not sure what "Info" menu you are talking about.
I would create bug report for this. Another developer might know better whether it is really a bug or not.
I believe the documentation is wrong
This image does seem a bit redundant, removing it is okay.
I made a fix in rBM6551
Fixed in rBM6552
I would leave for now, it can be addressed as part of #56342
I had a vision for what I wanted here but forgot what it was. Removed in rBM6553
I think this is a bug, I would report it.
This again looks like a bug.
You need to use object color in the viewport shading options
Seems like you accidentally pasted something. should be
.. _bpy.types.Object.track_axis:fixed in rBM6554@Alaska please make sure the images you update are properly sized:
https://docs.blender.org/manual/en/dev/editors/timeline.html#playback-popover
There is no need to make image an overly high resolution either as it slows down page loading times.
Images can be scaled using
:width:for example:Hi @jamjchai if you would like to use the Blender Documentation Project to apply for your class reach out to me via email: carlisle.b3d@gmail.com and I can help you with with something that would qualify for your requirements.
@Blendify
In the header of the workspace "Info" there's a option for "Info>Toggle selection". I probably could of been a bit more clear on that.
I did not change that image and on my local version of the documentation the size was not an issue. I will take a look at it when I start work on this project again (probably tomorrow).
Reported here: #76013 #76014
Found out it's ctrl to add. Updated it here: rBM6557
I've removed it here: rBM6557
I was talking about the option in this section of Blender:
Thank you for helping out.
Updating Manual images to 2.8Xto Updating Manual images and text to reflect changes made in Blender 2.8X@Blendify I've continued work on the manual and once again have questions. rBM6578
Note: I may need to take an extended break from this project in the near future. Personal things are popping up. I'm fairly certain I won't have this finished by the release of Blender 2.83 and I'm personally going to take a step back from making changes to the manual during bcon 4 and 5. Hopefully that break is long enough, but I may need longer.
On the topic of future releases and manual documentation. Should I wait for Blender 2.90 to enter bcon2 before starting work on updating the manual or do you believe the changes made during the end of bcon 1 will be so small that I should just start work then? I can't actually remember if Blender 2.90 will enter bcon 2 at the release of Blender 2.83.
What is "this distance". I assume it's the lights distance of influence, but I'm sure there's a better way of explaining this. I really don't use EEVEE much.
The reason I changed this is because it describes an effect where objects further away from camera become more transparent (blend with the world colour). This is a feature of Blender Internal so is no longer available.
Yes, currently it is just too much work for us to have both versions being worked on at once. Keep an eye on #76164 hopefully later this week I will update it with a list of changes needing documentation.
My bad thank you.
Updated in rBM6581 hopefully, it is clearer now.
I think that wording is good.
If there is a todo it will get done by someone eventually.
I created this page recently to fix another issue on a different page and didn't want to down the long hole of filling it in. It is meant for developers and it would be nice for developers to understand the available options but it is not a priotity at the moment.
Updated in rBM6582
See the comments that Brecht and I made on rBM6580
@Blendify
From a quick look, seems clearer. Thanks for updating it.
Understandable.
Thank you.
I've taken a look at the feedback and hope to have resolved the concerns.
Added subscriber: @jenkm
@Blendify I have updated the manual to describe the limitations with the Ctrl-G keyboard shortcut for creating new collections on the advice of @jenkm here blender/blender#53662#920071.
rBM6590
plus small fix to wording in:
rBM6593
I'm just posting this so you know. Just ask if you'd like me to change anything.
Removed subscriber: @jenkm
@Blendify - I've done a bit more work on the manual and again have questions.
Text: rBM6600
Image: rBM6599
Extra: rBM6601
All the little mistakes I fixed from my original commits: rBM6602, rBM6603
I still haven't finished updating the rendering section of the manual. I only have a few pages to do and it should all be included in the next commit. I've just been working on the manual in one long session and I just couldn't progress any further.
They don't show up in the web page. Is this a formatting error? What should I do about these?
I'm not entirely sure how to reproduce this and thus am unable to verify if it still works in Blender 2.8X. Are you able to take a look at it?
I'll leave it up to you to decide whether or not it should be integrated or left where it is.
The difficulties I had with picking a mesh to use was that the image will be viewed at a low resolution (E.G. 800x450) and the wireframe easily starts to take up a lot of pixels.
If we can't use that image I could always use suzanne.
From my own testing, this is no longer true if you're using the filmic color transform (the default in Blender 2.8X). Should I remove it?
Updating Manual images and text to reflect changes made in Blender 2.8Xto Updating Manual images and text to reflect changes made in recent versions of BlenderThese were unused, removed in rBM6605
I am a bit confused on this also and have not been able to get it to work.
Yes, this infromation should be included in the manual.
Examples from the Cloud are okay to use in the manual.
From my testing and unserstanding this is still true.
Thank you.
I've hidden it in this commit rBM6616. All the information is still there if someone wants to update it.
Where should I include the information? I was thinking about adding it to the glossary, but that's probably not the best place. Maybe add the information to it's own page? Or should I just redircet the user to the /intern/cycles/render/attribute.cpp file? (https://developer.blender.org/diffusion/B/browse/master/intern/cycles/render/attribute.cpp)
Updated in rBM6615
The definition for the name field should be expanded on the attribute node page.
@Blendify
Also, quick question. Blender 2.83 will be a LTS release. This means users of the LTS release will be referred back to the 2.83 manual when selecting the "Online Manual" buttons within Blender. Obviously I'm not going to get this tasked finished by the release of 2.83 which means the 2.83 manual will have some outdated information. What's the possibility of the 2.83 manual still being editable?
Obviously this would create a lot more work for me and other maintainers of the manual as any changes made to the 2.83 manual will also need to be carried over to the 2.90 manual and many images of the user interface will need to be produced separately for 2.83 and 2.90. But hopefully once the 2.83 manual has had all its images and text updated to reflect changes made in 2.8X, updates to the LTS manual will mostly be limited to fixes to spelling mistakes.
There is still some discussion on if 2.83 will be an LTS release https://lists.blender.org/pipermail/bf-committers/2020-May/050570.html
As you said it would be a lot of work to maintain both 2.83 and 2.90 so that will likely not happen.
Most of the manual content was already updated 2.8x obviously some smaller changes were missed, so I do not think it is critical for use to have this done for the 2.83 manual.
I would rather keep pushing forward than trying to make older versions perfect.
That makes sense.
@Blendify
Yet another patch and yet more questions:
Text: rBM6630
Images: rBM6629
I'm confused about the last part of that, "the color space should be set to None". Shouldn't it be "Non-color"? I'm unable to find a none option.
Should it be removed?
This question was answered with the help @jenkm
Where "rates" is a hyper link to a non-existent page. Doing a quick search I've been unable to find a page that contains the information needed. Are you able to take a look at it?
I haven't finished updating the "render" section of the manual. However, the information on the pages that are left kind of go over my head at the moment. I might take another look at it when I can think clearer or maybe just add it to my list of "needs checking by someone more knowledgeable".
Here was supposed to be a link to the "Rate" section in the same document.
Added subscriber: @jenkm
@jenkm That makes sense. Reading that part of the manual it's clear now.
What do you believe I should do to fix it?
Add
above the rates section then change the hyperlink to
Sorry, I'm relatively new to RST and have been primarily focused on working on updating images and fixing menu locations in the manual to reflect changes in 2.8X.
This should work as a link to the "Rate" section:
@jenkm Thanks for helping me out with this.
Committed with rBM6640
Yes, should be "Non-color"
No the information here just needs to be expanded explaining the different types of outputs, Animation, Render, Audio. And how to actually produce these outputs.
See the todo:
todo: describe the steps to output renders@Blendify
Fixed with rBM6648
Sorry, I didn't see that. I usually browse the pages in the web-interface then go to the .RST if I find a mistake.
Closed as duplicate of blender/blender#76705
@Blendify, I'm sorry, I accedentally merged this task with blender/blender#76705. Are you able to reopen this task? Or will I have to create a new task.
I'm unable to find the option to re-open/unmerge these tasks.
Changed status from 'Duplicate' to: 'Confirmed'
Thank you.
@Blendify Yet another patch and more questions:
Images: rBM6654
Text: rBM6655
Small fix: rBM6656
I haven't finished updating the compositing section yet. I plan to get that done this weekend.
Added subscriber: @EAW
You seem to be doing a lot of work on the bug tracker as a non-moderator. I fixed that for you. 😉
Thank you @EAW. I usually just help people on reddit who use Blender. But most of the time it's the same thing over and over again. So I decided to start looking at issues here as they're more interesting and can actually teach me a little. If it's something that's a mistake on the users part, I try and correct them. If the user doesn't provide enough information, I ask them to add some, just to save the developers the couple seconds it takes to ask the question and the potentially hours of waiting for a response (general moderator like tasks). Also, checking here on a regular basis helps with learning about upcoming and recently introduced features in Blender. Though, I also read the weekly reports for those as well.
I also started work on the updating the manual because:
Big thank you to you @EAW and all the other moderators and Blender developers for making Blender the software it is today. And for making it free.
I am guessing it is a configuration issue on your side.
I think this is a bug. I have it working in 2.79 and 2.81 but the same file doesn't work in 2.83.
@jenkm I will investigate it further, do some searching around on this site, and if I don't find anything, make a bug report. Unless you would like to make it.
@jenkm I'm unable to find any information so far about the issue. I'll make a report for it.
@Blendify Yet another patch. I'm sorry it took a while. I was going to get this patch committed last weekend but never got around to starting it. With bcon 3 ending in a few days (assuming no further set backs), this will most likely be my last commit for this task until the Blender 2.90 manual is available.
Text: rBM6678
Images: rBM6677
Thank you for all the help you have provided over the time I have been working on this task.
Should I remove the link or is this something you could fix by changing permissions?
blender/blender#29192#128154
blender/blender@1357f1b09f
My description reads:
If you think anything needs to be changed, just say so.
Movie Clip Editor ‣ Properties ‣ Stabilization ‣ 2D Stabilization ‣ Filter. I'm unable to find this in 2.79 or 2.83 (assume the in between versions are the same). However there is a option "Interpolate" which has the settings that's described on that page. So I have changed the manual to "Interpolate" as I believe this setting was renamed to that. If this is incorrect please correct me.That sound reasonable
I would leave these for now, will be addressed as part of #56342.
No sounds good.
It might be hard to find the exact frame but these images came from https://media.xiph.org/tearsofsteel/ you might also be able to find a couple of images on the Blender Cloud. You are still welcome to leave for someone else if you want.
Yes, just double-checked and it, at some point has been renamed.
Sorry, I got a bit of tunnel vision. Basically I wanted to use the same scenes as what was currently in the manual as I don't have any green screen footage I could use to recreate the image (as in, creating an example for the keying_screen node). I also didn't want to just go out onto the internet and find some green screen footage because licensing reason. And I kind of forgot about the Blender cloud.
I will look at the link you shared (files are quite big so will take a while to download). If I can't create a scene that works for the manual, I'll just skip over that section and leave it as a "TODO for someone else".
Thank you @Blendify for helping out. The keying screen section of the manual should now have up to date images: rBM6693
@Blendify
Just as a question, is the change in theming between the 2.82 and 2.83 manual intentional? Nothing in the rst files seem to suggest that some of these labels should have "blue boxes"
E.G.
2.82: https://docs.blender.org/manual/en/2.82/editors/3dview/controls/overlays.html
2.83: https://docs.blender.org/manual/en/dev/editors/3dview/display/overlays.html
2.82:
2.83:
That is not intentional. I will investigate later.
I applied the fixes again and reported upstream: https://github.com/readthedocs/sphinx_rtd_theme/issues/936
Thank you @Blendify
Just as a note on this task. I said I was going to take a break from the task during bcon 4 and 5 of 2.83 to ensure stability of the manual and to just take a general break due to personal things. Those personal things have grown and my break may have to extend to a few months, maybe even years or indefinitely.
I will try and do little bits here and there. Update a page or two from time to time, but my activeness in completing this task will probably be reduced.
No worries we have appreciated your help.
Removing myself as the assignee of this task so someone else can "officially" take over this task if need be.
As I noted above, I will try an continue to help out with this, but personal things are getting in the way at the moment.
Changed status from 'Confirmed' to: 'Resolved'
This is mostly resolved few remaining changes can be addressed in a specific task if necessary.