I'm not reproducing on my end,  but I'm also not sure what steps you are taking. In the video, I don't see any sort of dialogs appearing and the UI is too blurry to see any detail in the panels. Are you simply copy/pasting in the new layer? And once the new layer is created, the transform handle is just stuck to the cursor?    Looking at other posts from folks reporting similar behavior, I keeps seeing that third-party apps, such as Magnet, add this functionality on purpose. One thing that can determine whether or not this is the cause on your system is to run your computer in a simplified startup mode (see: https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd) ... View more

@David25770682iyzt I've tried the steps you've listed but I'm not seeing the same behavior on my end, I'm able to overwrite files without issue, I'm not losing anything. As Jeff mentioned, what you are reporting is not related to what this post is about, which was the reported file size was not changing when overwriting (which we have fixed). The video you've posted is impossible to see what is occurring. Can you recreate the behavior and tell your screen recording software not to capture both screens (if you are unsure how to do this, the easiest thing may be to unplug the secondary monitor while recording)?  ... View more

Thank you for posting. I am able to recreate the behavior on my end. I will work with our engineering team to get this fixed in a future version. For now, as a workaround, simply convert the shape layer(s) to Smart Objects. This will allow you the ability to edit the shape in the future but will also lock in the shape when you go to export.  ... View more

Yes, we did fix the clipping issue. For SVG, there are currently two paths (pun not intended):  1. Use Generator. Just add ".svg" to the end of the name of a shape or other vector layer with Image Assets turned on. I'm not sure why we don't mention SVG in our documentation here: https://helpx.adobe.com/il_en/photoshop/using/generate-assets-layers.html, but I just verified it still works.  2. Use Illustrator. This is more along the lines of what we are suggesting now but haven't released our documentation on it yet. This 3rd-party link covers the essential steps though: https://chasingheartbeats.com/photoshop-how-to-save-as-svg-file/ ... View more

Thank you for reporting these items. We changed the underlying codebase for Export As to make it more compatible for newer machines and make performance enhancements. This has resulted in some changes to how the tool behaves. First, the smaller text size is an indirect result of this codebase change. The new code uses a different library for UI elements, called Spectrum, which includes things like different weights for the fonts. This is not something we can change directly for just Export As and should be brought up with the Spectrum team. For more information on this, see: https://spectrum.adobe.com/ The zoom keyboard shortcuts are not a function Export As has supported. I'll add this as a feature request. The new Export As uses newer resize methods which result in sharper previews. Normally, sharper would be preferable to blurry, but in some images this may not be the case. If you could provide some examples or screen shots, that could help us make improvements.  The old Export As had a dependency on older technology within Photoshop that was used to provide SVG support. We are working toward removing this older technology from Photoshop and that meant removing it from Export As first. We should have documentation, including workarounds, but it doesn't look like it has been published yet. I'm working with the relevant team to see if we can get this corrected.  Nearest Neighbor is definitely exporting as Bicubic. I will have the team work on correcting this.  ... View more

Unfortunately, the display profile issue is another thing we are working on. The good news is that the exported file will be correctly color managed.  ... View more

I know this post is a bit old, but I've been going though our backlog and have some information on this issue. There are some issues with Smart Objects in Export As currently. One, the rendering of them creates wavy lines on the edges of objects. This is most noticeable on text and vector objects. Two, smart objects with a Warp Transform applied will seem to disappear. What is actually happening is that the embedded object gets transformed multiple times but the bounding box remains the same. The object moves outside of the box and is essentially masked out. You can work around these issue by not using smart objects for export (rasterize these layers or flatten the image). We are currently working on a solution.  Last, Todd's ratio changes: There is a limit of 2 decimal places in the math. For your example, 5616 / 1500 = 3.744. This gets rounded to 3.74. 5616 / 3.74 = ~1501.6, rounded up to 1502. We've updated Export As and it now handles the math better, you'll get the correct 1500. Just make sure you are using the newer version of Export As. Check your Preferences, either Technology Preview or Export. You should see the option to use "Enable Optimized Export As" in the former or "Use Legacy Export As" in later (not both) depending on the version of Photoshop. Turn the first one on or make sure the second one is off. When you run this upgraded version of Export As, you will see a version number near the Export/Cancel buttons.  ... View more

*peteharvey89 This is a bug in our older version of Export As. We are updating it to a new version soon but you can enable it now for a better experience . Simply go to Preferences > Technology Previews and check the  "Enable Optimized Export As" option. You should see the expected behavior from this point on. ... View more

You are likely looking in the wrong Preferences folder.  The system default preferences are stored in //Library/Preferences. Your Preferences are stored in //Users/[Your User Name]/Library/Preferences. This secondary Library folder (sometimes called "~/Library") is hidden by default and stores your personal settings files. See the following for ways to reveal the Library folder: Access hidden Mac OS library files ... View more

We've confirmed this behavior on our end. This has been reported to the engineering team for repair in a future release. ... View more

Yes, installing the module restores the exact same functionality as in the CS4 and CS5 versions of Bridge. ... View more

A one step process is go to Photoshop, File > Automate > Contact Sheet II. This was the original functionality before Bridge existed. A two step process is to select the files you want to work with in Bridge, then go to Tools > Photoshop > Contact Sheet II (this will send the files to Photoshop, pre-populating the dialog box with the files you have selected). A secondary one step process is to add the Output Module back into Bridge, which requires a two step setup process. The two steps are to download the required files and to move them to the correct folder locations. The files and those folder locations are provided here: How to install Adobe Output Module in Bridge CC 2017 ... View more

Bridge merely looks at the files on your hard drive. Lightroom merely catalogs image files. If you import your files from your camera into Lightroom, one of the settings for that import is choosing the location on your hard drive that the files will copied to (the default is your Pictures folder, in a collection of folders based on the date the images where photographed). In Bridge, simply navigate to the folder location where you've imported the images to. ... View more

I haven't tested the new update to see if this has changed. I'll check in with the Bridge team to see what the status is (whether this was fixed and should work for you or if there is still something holding this back for some reason). It works in Lightroom because Lightroom uses a very different set of OS APIs. The ones that Bridge use are much older and were deprecated by the Apple OS. Basically, the parts of the Mac that Bridge would borrow to communicate with the camera were removed. Since Lightroom used newer API that are still in the OS, there was no loss of functionality. Getting this to work in Bridge again would require an update to replace those APIs. Now that we have this update, they should be there, at least from the information I had at the time. But I haven't worked with the Bridge time for some time. So I'll have to get back to you on it. ... View more

Not sure why Firefox alone would not allow you to visit the page. I'm more of a Chrome person myself, so I don't really have any tips to provide. Also, Adobe does not code or host this site, we are simply using the services of GatSatisfaction.com, so they may be a better source for information on browser compatibility.  ... View more

Hello Matt. Unfortunately, Chris was unable to respond to this. However, I have now confirmed the behavior and will log this with the engineering team for repair. To note, this behavior is specific to the Windows side of things (you are able to resize both windows on Mac). ... View more

Thanks for the update ... View more

Have you tested with different files? ... View more

An I/O (input/output) error is a different beast altogether. These types of error occur when working with corrupted files, folders, and or disks. The first thing to do is test your source files. Try an output with fewer and different files. For example, download a couple jpegs from the internet to your desktop folder and work with those. If that works, you may need to find new copies of your source files. If this doesn't work, output to a different location, such as your desktop folder. If you are outputting to an external drive, try internal. Et cetera... ... View more

Hello Dennis,   Adobe does keep your log-in information stored locally. Just like a cookie stores your information in a web browser, we have a file that keeps your account info. The name of this file is opm.db. If you are continually being asked to login, it means this file is not being updated with this information. This can happen if the file is locked (by another process or by file permissions), damaged, or otherwise uneditable. The file is stored here:  --Windows: C:\Users\[user name]\AppData\Local\Adobe\OOBE --Mac OS: /Users/[user name]/Library/Application Support/Adobe/OOBE (NOTE: the AppData and Library folders listed here are normally hidden by the OS and must be revealed before they will appear in Explorer/Finder (respectively)).    1. Verify the presence of this file. If Photoshop is working, it suggests the file is there.   2. Make sure you have read and write permissions on this file. Again, with Photoshop working, it suggests you have at least read permission. But you may not be able to update the file with Lightroom information. (see: https://support.apple.com/kb/PH21997?locale=en_US&viewlocale=en_US)   3. Try logging out of and back into your account. Not through Lightroom itself (as this shouldn't even be necessary), but through the Creative Cloud desktop app. This should update the opm.db file with your current subscription information. See instructions here: https://helpx.adobe.com/creative-cloud/help/sign-in-out-activate-apps.html   4. If the above did not work, recreate the opm.db file. Sign out of the Creative Cloud desktop app, do not sign back in. Close the app. Navigate to and delete the opm.db file. Restart the app and sign in again. This will take a moment to redownload your account information.    Since the account information is stored locally, we do not sign you out of your account. Even if cancel your subscription, your account would remain logged in, as there are several free features that you would still have access to.  -Brett ... View more

Mike, it doesn't sound like you are using Lightroom correctly. First, Lightroom is a database, the catalog. It doesn't store your images, it stores information about your images. This includes where the file is stored on your hard drive. If you move the files from one hard drive location to another, changing folders, you invalidate the information that Lightroom has about your files. Thus, you have a database entry that says the file is in such-and-such location, but in reality the file is moved to a new location. At this point, you have to update the database with the correct location. If you try to work further with invalid information, you start to run into they type of trouble you report here. First, in the future, use Lightroom to move the images from one folder to another. Doing so not only moves the files to the new location on the hard drive as you want, but it keeps the database up to date with the correct and current information. More info on this is here: Move folders around in Lightroom | Adobe Photoshop Lightroom CC tutorials Next, if you have already moved your files around on the hard drive outside of Lightroom, you'll need to update the location within Lightroom. Details are given here: How to find missing photos in Photoshop Lightroom Going through the specific things you mention:  I manually copied photos from one folder to another and then tried to import them into the new folder. Again, don't do this, it causes problems. The files have already been imported, you can't import them again from a different location. It refuses to see them as new pics. That's because they aren't new pics, they're still in Lightroom. I tried to synch the folder and still does not add the photos. Syncing is not how you want to take care of this, because you stand to lose some of your work. You should be reconnecting the images, as described above in the second link I provided. But if you want to use sync (which is not what sync is really for), you have to sync the old folder first. This will update the catalog with the new information, that these images are no longer at this location. This would just be the same as deleting the files in Lightroom, it removes them from the catalog. The problem is that you will lose any work you've done (any edits, keywords, etc). Then you would sync the new folder so that you can update Lightroom with the new location. Again, this is the wrong way of going about things as it takes many extra steps and you lose information. In addition, I removed several photos and say delete from disk but they are still there. If you move a file outside of Lightroom, the file is now disconnected. Lightroom no longer has control of the original file on disk. Thus, Lightroom cannot delete the file from the disk. It doesn't know where the file is on the disk in order to do so. Instead, all you are doing is deleting the catalog reference to the file. This is what will let you sync the file from the new location. But again, you are losing work and also making more work for yourself. ... View more

Did you try creating a Bridge CC Extension folder? ... View more

The Output Module was never a "main function" of Bridge. There have been 6 versions of Bridge (CS2, CS3, CS4, CS5, CS6, CC). Of these only two had the Output Module as part of the basic installation (CS4 and CS5). Before Bridge was around and for the first two versions of Bridge (CS2 and CS3), Contact Sheets were created using Photoshop (in any version, you can use Bridge and Photoshop in combination to Create Contact Sheets by going to Tools > Photoshop within Bridge). We removed the ability to create Contact Sheets from Photoshop and they were instead created in Bridge through the Output Module (again, CS4 and CS5). However, our customers had grown accustomed to creating Contacts Sheets in Photoshop and wanted the original functionality back. For version CS6, we returned to the original behavior: Photoshop creates Contact Sheets, Bridge does not have an Output Module. Some of our customers liked the new way of doing things, so we provided a way of adding the Output Module back manually to CS6. This continued to be the way of providing this functionality in CC. So, those who have been creating Contact Sheets for a long time found chaos when we moved that functionality to Bridge. Those who like the new way of doing things have a way of continuing to do so. ... View more

Thank you for supplying a file. Unfortunately, this file seems to work fine on my side. That test is somewhat inconclusive though. There is only one layer in this file, so of course you can't delete the layer, you can't have zero layers in a file. There always has to be at least one or you don't even have a file. So I had to add a new layer before I could even attempt to delete the existing layer. Such a modification may change the nature of the file and thus nullify this test. Additionally, I don't have the font used to create this layer installed on my system, so technically, this is a somewhat invalid layer on my end. Could you supply another version of this (or another) file? It should have at least two layers (one you can delete and one you cannot) and if any Text layers are in use, make sure it is using a default system font. ... View more

For those that are seeing this issue on Mac after verifying that you have the correct files in the correct location, make sure that you have the actual files in the location and not an alias. And alias file will not work for this setup (although aliases work in some other situations). I've updated the document with information on how to check whether or not you are working with an alias. ... View more

I've added information about aliases to the documentation. This could be a sticking point for many. Let me know if my additions are helpful or require further changes. ... View more

I just tested this on my side, and yes, this will prevent the Output module from working. ... View more

Internesting. I see that your "Adobe Output Module" folder is actually an alias. That is what that little arrow in the lower left of the folder icon means. An alias is a substitute placeholder for the actual folder (on Windows these are called shortcuts). What it means is that the folder is not actually in this folder, it is somewhere else. What you'll want to do is move the actual folder to this location (and you are working with the correct location). Your workspace file is correct, it is the actual file and not an alias. This should be why you are able to select the Output module in Bridge, but it comes up blank.  ... View more

This generally means that the files that enable the Output module are not installed correctly. I only takes a single file to make "Output" appear at the top, but it takes a number of files in the correct location to make it work. Can you post a screen shot of where you've installed the files to? ... View more