Okay installed in other desktop and tested with one of the saved projects and Yes all images and folders are okay no images missing at all and all 46 pages are shown and working.

BUT it seems to take twice as long to actually open the project with all pages. Tested on other desktop that is not with new update and same project will open as normal in less time.
Ray

I've also noticed a significantly longer loading time of projects.

Thanks Inger I wondering if it was only me and yes seems to be significantly longer load time of project. Think I will wait before updating main computer to be safe ....maybe another update is around the corner.

Do you think because it is not a stand-alone like RFF that may be causing it? I only use Foundation none of the other ones.
Ray

In some instances of slowness, recent Wondows updates combined with certain antivirus software may be to blame. Details and possible preventive action are mentioned here.

Frank

Hello Frank,
Thanks for the info and url sounds almost like that could be the problem BUT it's only on the once desktop computer that I add it to for the test to see.
The V3.5 - 2939 on main computer the project with 47 pages opens on screen in 65 - 70 seconds.
The V3.5 - 2962 update on other computer with same project and 47 pages takes between 3 min to 3min 30 seconds to open on screen a big difference. After it does open all is fine and all images,resources and pages are thre working normally.
Both computers are same as far as anti-virus and setup.
Thanks for the link much appreciated.
Ray

Will wait a day or two and then send to support to see if it is an actual problem with new update.

Even opening a new project can take up to 2 minutes (which feels like hours.) If it was something with windows 10 & anti-virus stuff, wouldn't it affect everything my Dreamweaver opens like lightning, the only thing I have that is sluggish since the last windows update is Google Chrome,, that can take a minute or two ng..

Yes, I think it would affect the running of all substantial programs, as contrasted with small utility programs. I happened to be one of those that were badly affected by the Windows update until I found the solution referred to in the website mentioned in my post.

I have just tested timing in build 2962 on my old (not upgraded in any way for several years, though occasional hard-drive replacements have been made) self-built PC running Windows 10 as follows, starting without having opened the program since boot-up today (it's early morning here in the UK) -
1. Opening the program, at the Theme Chooser stage selecting my last small project, and opening it fully, took 25 seconds.
2. I completely closed the program, and then double-clicked on a 57-page Foundation-based RSD project file in Windows Explorer. Once again, from the original double-click to the full opening of the project took just 25 seconds.

My conclusion is that speed issues in build 2962 might have various causes. Some could be general problems such as the Windows update that affected me. Others could be conflicts with particular other software, and yet others could relate to particular factors within the project that is being opened - my projects contain only few image files, and they are fairly small ones. Ray's experience suggests that at least some of the problems afflict only this latest build of Site Designer. My experience suggests that not everyone has been caused speed issues with this latest build.

Frank

Machine: MacbookPro 2015 version, intel i7, 16 GB, 512 GB SSD
SD version: SD V3.5 2962
Loading: 1 page website (after converting to Materialize) in 4-5 seconds (including preparing workspace)
Loading: Materialize theme -about 23 pages- (Bob's component demo) in 30 seconds (including preparing workspace)
Loading: Flexbox guide in 4 - 5 seconds

I did not notice any substantial difference loading the Materialize theme between build 2962 and previous builds.

Hello all ..... it's Hans - just to give you a heads up, I have read (most of) this forum thread and I too had noticed the Materialize theme load a bit slow. I mentioned this to the developers and so we have this on our "check what's going on" list.

Thanks for letting us know and Ray and Hennie, thanks/bedankt for the documented testing benchmark

Hans