I've been looking into this for a day or two now. I've found other people who have had similar problems in this thread. According to the "Where to download" section of this minecraft wiki there is a known problem of black screens on 64-bit machines using LWJGL since v2.8.1. I've tried using older versions of LWJGL with no luck; I'd still get the black screen. Does anybody have a solution to get this working on a 64-bit machine?
Related
Is there a list of supported/un-supported graphic cards for WebGL2?
I am encountering a problem in two computers, both running Win7 with Chrome 58 (tested on 56 too), with all the WebGL flags enabled, one computer has nvidia quadro 600 and the other ati radeon HD 2400, both with latest drivers and I get an error that the browser doesn't support WebGL2.
I used the khronos' conformance test at: https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html?version=2.0.1
Anyone encountered a similar problem?
Thanks!
FIRST my Reputation is to low i cant post more then 2 links. Don't worry we find a way around Copy+Paste the text/that/might/look/like/a/link
Type
chrome://gpu/
into the adressbar and you see how good Chrome communicate with the Graphiccard and what task it can perform. - here are some switches to enable and tweak your default(if blacklisted) configuration:
peter.sh/experiments/chromium-command-line-switches/
Take into account
superuser.com/questions/836832/how-can-i-enable-webgl-in-my-browser
Also on Windows OpenGL/WebGL content has to transpile through so called ANGLE interface into DIRECTX. Probably the bug occurs on side of DirectX. Your GraphicCard was listed in ANGLE only for DirectX Version 10. and WebGL 1.0 You can bypass and start using native OpenGL by using the switch
--enable-unsafe-es3-apis
Try Chrome from a Dev channel/Canary.
the problem may fixed in an upcoming stable Version of Chrome
chromium.org/getting-involved/dev-channel
I have an acer switch alpha, and both Ubuntu and Debian worked flawlessly with the stylus. But I cannot get it to work at all on Fedora which is my preferred OS.
What works:
Hovering
Clicking on anything related to the gnome-shell (settings, activity bar, title bar) But nothing inside windows aside from the settings application so far.
Very odd behavior, am I missing some libraries?
Honestly the amount of time I waste debugging Fedora over the last few years is a bit much. Never had as many problems on Ubuntu or Debian will probably just swap considering how utterly unreliable Fedora has become.
As of Fedora 25, the distro defaults to booting into a Wayland-powered desktop. Pens are not well supported under Wayland at the moment; only native GTK3 applications such as the shell and GNOME Control Center will react to pen input (many applications either still use GTK2 or another toolkit like Qt).
Until the situation improves, I would recommend using the "gear" icon on the login screen to change your session from "GNOME" to "GNOME on Xorg". The pen should return to functioning as it has in the past.
I have a web server running Windows Server R2 Standard, and am experiencing the issue described in this blog post: http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
In short, .Net is failing to recognise IE10 and is treating it as a downlevel browser without javascript support - if I understand the issue correctly.
I tried the following popular solutions:
Installed both hotfixes for .Net 2 and 4.
Manually updated the browser definition files in the .Net framework config folder and ran aspnet_regbrowsers.exe.
Put the new browser definition files in the App_Browsers directory.
Finally I upgraded to .Net 4.5 which solved the issue for .Net 4 sites running on the server, however .Net 2 sites are still experiencing the issue.
Because this is a live web server it has a lot of windows updates that have not been installed. I thought maybe there was an update that would address the issue. So I've taken a look at the updates but none of the descriptions seem to address the issue, so I cannot justify installing them and potentially causing more problems.
Does anyone have any other solutions or possible reasons why this issue just won't go away?
I have the same problem, and I haven't been able to figure out why none of the fixes work. However, I did find a workaround that might work for you: Setting the Page.ClientTarget attribute to "uplevel" overrides .NET's browser capability detection. Have a look at http://msdn.microsoft.com/en-us/library/system.web.ui.page.clienttarget.aspx for more information.
Have come through many microsoft hot fixes, they were working in local environment, but in the live server there was no result.
Setting up Page.ClientTarget = "uplevel" (preferably in a header or footer page) has really solved the issue. I think this the best solution, as your .net application may not detect any other browser in future. But then we may have to wait and see, if this fix has any side effects.
I'm involved in some browser-compatibility testing, and we're looking at tools and so forth. One thing we need to do is visual inspection of our site in a range of different browsers on different OSs and platforms.
My question is whether there are documented differences (or someone can post some HTML+CSS) where a page will render differently in IE6 on Windows 2000 than it will in IE6 on Windows XP (say). Or IE7/XP vs IE7/Vista. Or Safari4/MacOSX Leopard vs Safari4/MacOSX Snow Leopard.
We're hoping to be able to slim down the count of combinations.
I've seen this other SO question, and don't think it's quite the same thing. The answers direct me to quirksmode.org. We're not looking for a breakdown of which elements/CSS-rules are supported in which browsers; we've got an existing site that for better or worse uses what it uses, and we'd like to get it under test to be able to make changes more safely.
You can submit to http://browsershots.org/ multiple times, eventually a different OS version will get called for the same browser version. This is not the ideal solution.
I know application questions belong on super user but since this is an IDE I thought I might try it here.
For a couple months now, MonoDevelop likes to appear on my second monitor maximized when I start it up. I have to unmaximize it and move it over each time.
I thought it was some weird preference setting I had messed with but I recently install Windows 7 and the first thing I did was get Monodevelop back up and running. It still goes to that second screen.
Anyone know why?
It might be a GTK+ Gdk.Screen issue. AFAIK none of the core MD devs have dual-screen setups - and definitely not on all platforms. Best thing to do would be to file a bug.