Images display correctly in XVCapture, but are out of order in XVWeb
Behavior:
When viewing a series within XVCapture, the images are displayed in their proper tiles, but when viewing the same series in XVWeb, some images appear underneath the layout, display in a grid, are scrambled, or appear to be displaying in the incorrect layout.
Causes:
All cases where images display correctly in XVCapture but do not in XVWeb are due to some form of disparity between the layout used in XVCapture and the available layouts in XVWeb. XVWeb utilizes the captured images' tooth associations to determine what layout to display the images in, as well as modality to determine what layouts can be used. A few common example causes are as follows:
- Images were captured in a layout that exists in XVCapture, but the same layout does not exist in XVWeb, causing the images to automatically display in the wrong layout or within a grid due to a lack of matching tooth associations.
- A partial series was captured (e.g. 7-9 images out of an FMX-18 on only one side of the patient's mouth), causing XVWeb to display the images in a layout other than an FMX-18 due to a combination of tooth associations and number of images matching with a different layout.
- The matching layout in XVWeb does not have the same tooth associations as the layout used in XVCapture.
- The tiles in the matching layout in XVWeb have a modality different from the image type that was captured. (e.g. the images captured in XVCapture were assigned IO modality, but the tiles in the matching layout in XVWeb have the modality XC assigned to them instead of IO)
Solutions:
- Ensure the layout used in XVCapture has also been created and exists in XVWeb, and both layouts have matching tooth associations.
- For example, if you've used a custom 4 Bitewing 3 PA layout in XVCapture, but the exact same layout with the same tooth associations does not exist in XVWeb, a layout matching the layout used in XVCapture needs to be created in XVWeb to allow the images to display properly. Please refer to Creating Custom Layouts - XVWeb for instructions on creating a matching layout.
- If needing to edit an existing layout to match the XVCapture layout's tooth associations, refer to Editing Layouts - XVWeb instead.
- If affecting a partial series of images, use the Layout > Place tool in XVWeb to reorganize the images into the preferred layout.
- If the images continue to display the same way after using Layout > Place, Layout > View will need to be used instead. This is not a permanent change, and only affects how the images are displayed while actively viewing them.
- Ensure the tiles in the matching layout in XVWeb are assigned the same modality as the images you have captured, to allow XVWeb to display the images within that layout.
- Refer to Editing Layouts - XVWeb for instructions on changing the tiles' modalities.
________________________________________________________________________________________________________________
Converted or imported images display in a grid instead of a layout
Behavior:
When viewing a series of images that were converted from a previous imaging software, or a series of images that were manually imported, the images display without order in a grid format.
Causes:
- The converted or imported images are missing tooth associations.
- The imported images were imported as a group of single images, or imported into a layout that does not have tooth associations and/or instance numbers.
Solutions:
- Converted images that are missing tooth associations will need to be manually placed into a layout in order to assign them tooth associations. This is done by using the Layout > Place tool to place the images into the preferred layout, which also updates the images' tooth associations.
- Layout > Place can also be used on images that were manually imported as a group of single images.
- If importing images into a layout, ensure the layout you are importing the images into contains tooth associations. If no tooth associations are needed (e.g. for an ortho layout), ensure the layout has progression instance numbers assigned, which will tell XVWeb which tiles to place the images into based on order.
- Refer to Editing Layouts - XVWeb for instructions on changing or adding tooth associations or adding progression instance numbers.
________________________________________________________________________________________________________________
Shot sequence order incorrect - XVWeb Capture only
Behavior:
When capturing images within XVWeb Capture, the order the user is prompted to capture images in is incorrect.
Cause:
The progression instance number on each tile in the layout being used for capture is either missing, or needs to be changed.
Solution:
Edit each tile's progression instance number to match the order you would like to capture your images in. Refer to Editing Layouts - XVWeb for instructions on editing or adding progression instance numbers to a layout's tiles.
________________________________________________________________________________________________________________
Certain layouts missing from layout selection window during image capture - XVWeb Capture only
Behavior:
When initiating a capture sequence via XVWeb Capture, the layout you would like to use does not show up in the layout selection window.
Cause:
The layout you are looking for has a modality different from what the device you are using to capture images will produce.
- For example, when capturing with an IO camera using the Intraoral Camera plugin, the expected modality will be XC. Therefore, only XC modality layouts will be selectable for use. When capturing with a sensor of any make/model, the expected modality will be IO, meaning only IO modality layouts will be selectable.
Solution:
Create a layout in XVWeb where all tiles have the modality that will be produced by the device you are using. Refer to Creating Custom Layouts - XVWeb to create the layout you need.
- For example, if you are looking to capture into a FMX-18 layout using an intraoral camera, you will need to create a FMX-18 layout where all tiles modalities will be XC instead of IO.