Jump to content

Ansariel Hiller

  • Content Count

  • Joined

  • Last visited

Community Reputation

931 Excellent


About Ansariel Hiller

  • Rank
    Certified Butt and Code Shuffler

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Contact the creator of that game and ask them to change your username in their database to your new one since they are apparently "very smart" and use a username as key in their database instead of your account's UUID...
  2. 32bit viewers don't set Windows 10 compatibility to allow people with older Intel HD2000/3000 GPUs to be still able to use Second Life, which results in Windows identifying itself to those viewers as Windows 8. Apart from that, I would check the dual GPU settings in the nVidia command center instead of that Windows settings thingy. I wouldn't trust that any inch.
  3. Nope, wrong! Since I have an old laptop here with an Intel HD 3000 GPU and Windows 10 running on it, I can easily demonstrate how much of a driver there is: The driver comes directly with Windows 10 and is not the base driver Windows installs if it doesn't have a specific driver for the GPU. The only problem with this driver is that the actual Windows 10 profile is broken (presumably because Intel never provided full Windows 10 support), so you MUST run the application in Windows 8.1 compatibility mode, which - as already stated - does not work if you define explicit Windows 10 compatibility via application manifest. So again: If you want to run SL on a computer with Intel HD2000/3000, you either need to install a 32bit version or you need a 3rd party tool to remove the application manifest file from the viewer's executable to run the application in Windows 8/8.1 compatibility mode.
  4. The viewer is running perfectly fine in Windows 8.1 compatibility mode. The problem is that the executable file is explicitly configured to be compatible with Windows 10, which will result in Windows not trying to run the viewer in compatibility mode (if you don't specifiy explicit Windows 10 compatibility, an application will always run in Windows 8 (or 8.1) compatibility mode). This is done by a so-called application manifest file, which is built into the executable file. Not sure how it is done in Singularity, but both the LL viewer and Firestorm do not set Windows 10 compatibility for their 32bit versions exactly because of the issue with older Intel GPUs. If you are confident enough to mess with the executable file, you can install something like Resource Hacker and remove the application manifest file from the executable: https://gyazo.com/723db0f986d5e1392330eb4f53eba58c The screenshot shows where to find it for the LL viewer, but should be identical in Singularity. If you remove the "1 [English (United States)]" item and save the changes, the viewer should start in Windows 8 compatibility mode next time and work with the HD 3000 GPU.
  5. Use a viewer with client-side automation script support via LUA, e.g. CoolVL.
  6. I simply installed Open Shell - gives you the classic (usuable) start menu and gone are those apps.
  7. @cheesecurdPlease show where I advise people should move to Windows 10 in particular? Thank you! What I am saying all the time is: Move on from Windows 7 to something else that get regular security updates and don't put yourself at unknown security risks!
  8. @cheesecurdcan you please stop advising people to stay on Windows 7? If you want to waste spend time trying to prevent your installation becoming a time bomb for yourself and everyone else, then it's your thing. But that's nothing the normal user wants to and will do. But telling everyone else it's save to continue using it is the same kind of advice like telling people it's a good idea to drive a car without using a seatbelt. Saying that: Good luck with your Windows 7.
  9. Why should LL rethink their decision? It's not that they disallow connecting people still using Windows 7. And it's not that nobody knew Windows 7 will reach its end of life in 2 days - that was known for several years! Microsoft even added warnings in Windows 7 informing users for the several past months! The people now coming out of their holes and complaining about it are pretty much ridiculous - like sitting there for at least 5 years knowing this day would come, but instead of preparing they apparently resorted to praying and hoping. Sorry to say, but there is nobody to blame except for yourselves. There was time enough to think of a solution - and still is in terms of connecting to SL - even for people low on money.
  10. Apart from whether it's a good idea to have more picks: This isn't the place to request them as only moderators are reading this forum. You need to file a request at https://jira.secondlife.com for that.
  11. Being a TPV developer I can assure you nobody is gonne put time and effort into making it work great with wine for like <2% of all users.
  12. Not necessarily, Oz! I was once at a place where I could only login if I deleted the inventory cache prior, but then could stay logged in without any issues. For whatever reason the UDP simulator messages got dropped during login in that case.
  • Create New...