On my alienware it is a Nvidia setting to use its driver as default and can
also be set for a specific *.exe program name.
On Fri, Jun 30, 2017 at 10:26 AM, Jonathan Welch <jhwe...@gmail.com> wrote:
> Some systems have two built in graphics chips such as Lenovo laptops with
> a system called Optimus. One graphics chip is very weak and the other much
> stronger, bit also more power hungry. As I recall it took a while to
> register the .EXE name with Nvidia so the stronger chip runs the viewer.
>
> Is this registration underway already?
>
> On Jun 30, 2017 9:23 AM, "Nat Goodspeed" <n...@lindenlab.com> wrote:
>
>> On Fri, Jun 30, 2017 at 6:36 AM, Nicky Perian <nickyper...@gmail.com>
>> wrote:
>>
>> I may be jumping ahead, but with an opensource build and built installer
>>> used :
>>>
>>> With shortcut to "C:\Program Files\SecondLifeProjectAlexIvy\SL_Launcher.exe"
>>> --set InstallLanguage en
>>> Program does not run log follows:
>>>
>>> 2017-06-30T09:56:59Z INFO: update_manager.py(261) : getBitness: Setting
>>> bitness to 32 due to HD Graphics Win 64 Bit incompatibility.
>>>
>>
>> This is the key log line here. We have reports that certain graphics
>> cards do not play well at all with our Alex Ivy 64-bit viewer.
>>
>> The new Viewer Management Process component of Alex Ivy (SL_Launcher) is
>> a small program that runs first to manage updates and so forth. This is the
>> VMP trying to optimize your user experience by downloading and installing
>> the corresponding 32-bit viewer.
>>
>>
>>> 2017-06-30T09:57:00Z INFO: update_manager.py(354) : query_vvm:
>>> Requesting update for channel 'Second Life Project Alex Ivy' version
>>> 5.1.0.171810121 platform win32 platform version 10.0.15063 allow_test
>>> testok id 8ff7c019124918cd78f655542a14c58e
>>> 2017-06-30T09:57:01Z INFO: update_manager.py(361) : query_vvm: received
>>> result from VVM: {'platforms': {}, 'required': True, 'version':
>>> '5.1.0.171810121', 'channel': 'Second Life Project Alex Ivy', 'more_info':
>>> None}
>>>
>>
>> Aaaaand here's the thing: you're running a self-built viewer. Our Viewer
>> Version Manager knows nothing about it and cannot provide the corresponding
>> 32-bit viewer for you.
>>
>>
>>> 2017-06-30T09:57:01Z WARNING: update_manager.py(398) : query_vvm:
>>> Unexpected response - no data for platform 'win32': {'platforms': {},
>>> 'required': True, 'version': '5.1.0.171810121', 'channel': 'Second Life
>>> Project Alex Ivy', 'more_info': None}
>>> 2017-06-30T09:57:01Z ERROR: update_manager.py(401) : query_vvm: Error
>>> from reading VVM response: KeyError('win32',)
>>> 2017-06-30T09:57:01Z ERROR: update_manager.py(411) : query_vvm: Could
>>> not obtain 32 bit viewer information. Response from VVM was {'platforms':
>>> {}, 'required': True, 'version': '5.1.0.171810121', 'channel': 'Second Life
>>> Project Alex Ivy', 'more_info': None}
>>>
>>
>>
>> With shortcut pointing to "C:\Program Files\SecondLifeProjectAlexIvy
>>> \SecondLifeProjectAlexIvy.exe"
>>> Runs OK.
>>>
>>
>> That's useful information: we should probably refine our graphics
>> card/driver test to allow running 64-bit Alex Ivy on your configuration.
>> Please file a Jira with pertinent graphics card/driver information and the
>> statement that 64-bit Alex Ivy runs well for you?
>>
>> But in general, please don't hack the shortcut. We've moved all the
>> update machinery from the viewer executable to the separate SL_Launcher
>> program. If you directly run SecondLifeProjectAlexIvy.exe, you will not get
>> updates.
>>
>> There are several useful things about having a whole separate program to
>> manage updates. The most basic of them is this: SL_Launcher is a 32-bit
>> program, even in 64-bit viewer installs. Even if a user running 32-bit
>> Windows downloads a 64-bit installer, s/he can still run SL_Launcher, which
>> will determine that the 64-bit viewer can't possibly run and will download
>> and run the corresponding 32-bit installer.
>>
>> Because there are graphics cards/drivers that apparently don't play well
>> with 64-bit Alex Ivy, we use that same logic to ensure that users with
>> those cards/drivers use the 32-bit viewer instead. I'm glad to hear the
>> test is overly pessimistic in some cases.
>>
>> All this machinery is still brand-new. We naturally must ensure that
>> developers can run self-built viewers without undue difficulty. You can
>> understand, though, that our initial focus has been on end-users.
>>
>> _______________________________________________
>> Policies and (un)subscribe information available here:
>> http://wiki.secondlife.com/wiki/OpenSource-Dev
>> Please read the policies before posting to keep unmoderated posting
>> privileges
>>
>
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges
