Processing Ajax...

Title

Message

Confirm

Confirm

Confirm

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure?

User Image
Matx77
5 discussion posts
Hi,

I have installed the latest beta 7.3 beta 3, and on my second monitor the start menu will not open.

When I click on the start button it doesn't load, whether I'm using classic shell or the normal win 10 menu.

Would you be able to provide a link to previous beta 2 version?

Thanks.
Sep 1, 2015  • #1
mikeyw's profile on WallpaperFusion.com
Same thing is happening to me on two different machines. One runs Start10 and the other one runs Classic Shell.
Sep 1, 2015  • #2
Jon Tackabury (BFS)'s profile on WallpaperFusion.com
Thank you for letting us know, we'll look into that issue for the next beta coming soon. :)
Sep 1, 2015  • #3
User Image
Henrik Bo Andersen
17 discussion posts
Same here. Two monitors showing W10 menu and primary monitor (laptop) showing Classic Shell.
Sep 1, 2015  • #4
User Image
Jaga1
15 discussion posts
Quote:
Thank you for letting us know, we'll look into that issue for the next beta coming soon. :)


Correct me if I'm wrong, but isn't something like this a candidate for a hotfix? Given the large number of bugs/problems with Beta3 (especially on W10), the software is a pretty good candidate for simply uninstalling at this point.
Sep 1, 2015  • #5
mikeyw's profile on WallpaperFusion.com
Thanks for the update Jon. Not a big deal, since the Win10 menu is fine once you get used to it.
Sep 1, 2015  • #6
Jon Tackabury (BFS)'s profile on WallpaperFusion.com
Beta 4 is out now, does it help with this issue at all?

@Jaga1: Beta versions have bugs, they're for testing new features. We're working on resolving the issues as fast as we can so we can ship 7.3.
Sep 4, 2015  • #7
User Image
Jaga1
15 discussion posts
Quote:
Beta 4 is out now, does it help with this issue at all?

@Jaga1: Beta versions have bugs, they're for testing new features. We're working on resolving the issues as fast as we can so we can ship 7.3.


I'm not new to software development, let's just leave it at that.

I was making a point that the Start menu not appearing where it should dramatically impacts the usefulness of the software as a whole. i.e. it becomes very inefficient to use at that point. When your entire package is nearly worthless due to a single feature, usually you hotfix that feature giving it priority status, even in a beta.

I've seen one of the 6+ problems I've experienced with the 7.3 beta branch fixed in a week's time. I'm going to uninstall DisplayFusion until more progress is made. I simply can't use it with Windows 10, because it doesn't work with Windows 10.

The odd part - you guys had what, 9 months+ to mess with W10's Technical Preview, then 30+ days after release? This is truly disappointing. DisplayFusion is the *only* piece of software I'm using on W10 that has major issues.

A note: if you're going to have a box with a link to the Windows 10 known issues topic, you should probably update that list to reflect the true status. Anything else is either inept, or dishonest marketing.

And no, Beta 4 doesn't fix this problem. I'm almost certain I posted this elsewhere on these (or the Steam) forums yesterday.
Sep 5, 2015  • #8
Keith Lammers (BFS)'s profile on WallpaperFusion.com
We've just released a new DisplayFusion beta version (http://www.displayfusion.com/Download/Beta/) and this issue should be all fixed up. Please let us know if you run into any trouble after updating.

Thanks!
Sep 10, 2015  • #9
User Image
Henrik Bo Andersen
17 discussion posts
Same story with beta 5. Two monitors showing W10 menu and primary monitor (laptop) showing Classic Shell. When using Windows own multimonitor taskbar there's no problem, Classic Shell on all monitors. :-[
Sep 10, 2015  • #10
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ok, strange! There was definitely an issue in Beta 4 that we fixed up for Beta 5. Sounds like your issue may be a different one then. Could you send over a debug log?
  • On the Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal"
  • Restart DisplayFusion
  • Try to open the Start menu on the second moniotr and note the time so we'll know where to check in the log file
  • Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
  • Disable debug logging after sending the log
Sep 11, 2015  • #11
User Image
Matx77
5 discussion posts
The latest beta 5 is working fine with classic shell, and the normal win 10 start menu.

Only issue I have noticed is the custom start icon I'm using is smaller on the displayfusion taskbar, unlike in version 7.2 where it’s the correct size.

Thanks again.
Sep 11, 2015  • #12
User Image
Henrik Bo Andersen
17 discussion posts
Here's the logs. Startmenu was activated 13:59:01.
• Attachment [protected]: DebugInfo.html [153,867 bytes]
• Attachment [protected]: DisplayFusion.log [4,204,543 bytes]
Sep 11, 2015 (modified Sep 11, 2015)  • #13
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@Mat: Which Start button icon are you using?

@Henrik: Thanks! Do you have "Replace Start Button" disabled in Classic Shell?
Sep 11, 2015  • #14
User Image
Henrik Bo Andersen
17 discussion posts
Yep, it's unchecked.

I just discovered, that if I replace the Start button, the Classic Shell shows on all 3 taskbars. Problem solved :laugh:
Sep 11, 2015 (modified Sep 11, 2015)  • #15
User Image
Matx77
5 discussion posts
Quote:
@Mat: Which Start button icon are you using?


At the moment here is some of the start button .bmp images I'm using;

http://medi-dadu.deviantart.com/art/Win-Start-Orb-289984133

http://effe8.deviantart.com/art/start-button-orb-windows-8-style-1-1-351806771

The only program I’m using is classic shell to change the default start button. But like I said in the latest betas the display fusion start icon comes out smaller, than on the normal taskbar.

Thanks again:)
Sep 11, 2015 (modified Sep 11, 2015)  • #16
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ok, thanks! I think this is due to another fix we had to do for the Classic Shell start button, unfortunately :(

I've put this on our list as well, and we'll see if we can fix it up without breaking the other fix again :)
Sep 14, 2015  • #17
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)