I've been developing an opengl nacl thing fine for the past couple of
weeks - suddenly this afternoon the gl stopped working. Native Client
programs still run, but no graphics display, in the samples I've
looked at - including tumbler and ogre3d - so it isn't my code, it's
something changing in the browser...
Things I've tried:
checked about:plugins and about:flags
checked my command line to make sure --enable-accelerated-plugins and
--enable-nacl are still there
checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV =
1
shutting down my computer and restarting it
What could I be missing? What have I done to mess things up?
Is it possible that chrome auto-updated to a different, not-working,
version?
About says it's 14.0.835.109 beta-m - I think that's the version I was
running before but am not positive.
OpenGL is not supported in Chrome/NaCl ... yet. There are plans to support it in Chrome M15 - I would suggest you check out an M15 Canary build and try that. The 3D API is still changing.
On Thu, Aug 25, 2011 at 6:10 PM, Jamie Fristrom <jdfrist...@gmail.com>wrote:
> I've been developing an opengl nacl thing fine for the past couple of > weeks - suddenly this afternoon the gl stopped working. Native Client > programs still run, but no graphics display, in the samples I've > looked at - including tumbler and ogre3d - so it isn't my code, it's > something changing in the browser...
> Things I've tried: > checked about:plugins and about:flags > checked my command line to make sure --enable-accelerated-plugins and > --enable-nacl are still there > checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV = > 1 > shutting down my computer and restarting it
> What could I be missing? What have I done to mess things up?
> Is it possible that chrome auto-updated to a different, not-working, > version? > About says it's 14.0.835.109 beta-m - I think that's the version I was > running before but am not positive.
> -- > You received this message because you are subscribed to the Google Groups > "Native-Client-Discuss" group. > To post to this group, send email to > native-client-discuss@googlegroups.com. > To unsubscribe from this group, send email to > native-client-discuss+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/native-client-discuss?hl=en.
> I've been developing an opengl nacl thing fine for the past couple of
> weeks - suddenly this afternoon the gl stopped working. Native Client
> programs still run, but no graphics display, in the samples I've
> looked at - including tumbler and ogre3d - so it isn't my code, it's
> something changing in the browser...
> Things I've tried:
> checked about:plugins and about:flags
> checked my command line to make sure --enable-accelerated-plugins and
> --enable-nacl are still there
> checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV =
> 1
> shutting down my computer and restarting it
> What could I be missing? What have I done to mess things up?
> Is it possible that chrome auto-updated to a different, not-working,
> version?
> About says it's 14.0.835.109 beta-m - I think that's the version I was
> running before but am not positive.
Looks like it is due to some API changes so if your code (as our) was based on the Tumbler initially you may have to fix up that. I am going to try and change our code later today and see if that is indeed the problem.
Those are straight off our build bots so who knows what bugs are in them but I use them quite often.
Generally I download to the same place and unzip in the same place. For windows I have a shortcut that I pass a bunch of options. For mac I have a script 'chrometest' (below)
An important one for me is --user-data-dir=somefolder. That way the prefs and cache and other stuff from these unstable versions of Chrome don't mix with my stable version
Note, those versions are of Chromium, not Chrome, so certain features that can't be made open source are not available. Sorry, I don't have a list of what those might be but I haven't run into any issues because of that yet.
> Looks like it is due to some API changes so if your code (as our) was based > on the Tumbler initially you may have to fix up that. I am going to try and > change our code later today and see if that is indeed the problem.
Please note that the tumbler example has been updated and in the examples directory in the SDK repo. It's hasn't made it into an official release of the NaCl SDK yet. The important changes are the move to use pp::Graphics3D_Dev to manage the context and surface.
The old tumbler example code was under experimental while the APIs were in flux.
Note that pp::Graphics3D_Dev is still a Dev interface. This means it's subject to change without notice, and that 3D might not always work in Chrome.
> To post to this group, send email to > native-client-discuss@googlegroups.com. > To unsubscribe from this group, send email to > native-client-discuss+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/native-client-discuss?hl=en.
Sorry, I failed to make clear just how weird what I'm seeing is.
Everything was working and then it wasn't. I never updated the sdk -
I'm still using 0_5_984. I'm not using the canary Chrome, I'm still
using 14.0.835.109. And these aren't just my projects I'm having
trouble with. The ogre3d and tumbler sample that Assaf put up, for
example, load but don't render. They used to render for me, and then
something just ... changed ... yesterday.
(Assaf, do they still work for you? What version of Chrome are you
using?)
It's as if Chrome is just ignoring the --enable-accelerated-plugins
command line parameter.
Yes, I tried restarting my machine. I tried uninstalling and
reinstalling chrome. I tried a couple of different ways of passing the
command line to Chrome. I've only got one monitor. WebGL still works.
Sorry about this. If I were you I'd dismiss it as *some* kind of
operator error, and I'm sure it is, I just don't know what, and don't
really expect you to be able to help, but don't know what else to try
at this point.
Any other ideas?
On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote:
> I've been developing an opengl nacl thing fine for the past couple of
> weeks - suddenly this afternoon the gl stopped working. Native Client
> programs still run, but no graphics display, in the samples I've
> looked at - including tumbler and ogre3d - so it isn't my code, it's
> something changing in the browser...
> Things I've tried:
> checked about:plugins and about:flags
> checked my command line to make sure --enable-accelerated-plugins and
> --enable-nacl are still there
> checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV =
> 1
> shutting down my computer and restarting it
> What could I be missing? What have I done to mess things up?
> Is it possible that chrome auto-updated to a different, not-working,
> version?
> About says it's 14.0.835.109 beta-m - I think that's the version I was
> running before but am not positive.
I have a feeling (a chrome dev should probably confirm) that a new version of 14 was pushed to beta channel that is now no longer supports the way we were creating surfaces, and is instead using pp::Graphics3D_Dev.
> Sorry, I failed to make clear just how weird what I'm seeing is. > Everything was working and then it wasn't. I never updated the sdk - > I'm still using 0_5_984. I'm not using the canary Chrome, I'm still > using 14.0.835.109. And these aren't just my projects I'm having > trouble with. The ogre3d and tumbler sample that Assaf put up, for > example, load but don't render. They used to render for me, and then > something just ... changed ... yesterday. > (Assaf, do they still work for you? What version of Chrome are you > using?) > It's as if Chrome is just ignoring the --enable-accelerated-plugins > command line parameter. > Yes, I tried restarting my machine. I tried uninstalling and > reinstalling chrome. I tried a couple of different ways of passing the > command line to Chrome. I've only got one monitor. WebGL still works.
> Sorry about this. If I were you I'd dismiss it as *some* kind of > operator error, and I'm sure it is, I just don't know what, and don't > really expect you to be able to help, but don't know what else to try > at this point.
> Any other ideas?
> On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote: > > I've been developing an opengl nacl thing fine for the past couple of > > weeks - suddenly this afternoon the gl stopped working. Native Client > > programs still run, but no graphics display, in the samples I've > > looked at - including tumbler and ogre3d - so it isn't my code, it's > > something changing in the browser...
> > Things I've tried: > > checked about:plugins and about:flags > > checked my command line to make sure --enable-accelerated-plugins and > > --enable-nacl are still there > > checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV = > > 1 > > shutting down my computer and restarting it
> > What could I be missing? What have I done to mess things up?
> > Is it possible that chrome auto-updated to a different, not-working, > > version? > > About says it's 14.0.835.109 beta-m - I think that's the version I was > > running before but am not positive.
> -- > You received this message because you are subscribed to the Google Groups > "Native-Client-Discuss" group. > To post to this group, send email to > native-client-discuss@googlegroups.com. > To unsubscribe from this group, send email to > native-client-discuss+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/native-client-discuss?hl=en.
By the way, although they probably can't confirm anything (they don't comment on schedule), I think the NaCL SDK team is on a 4-6 week release cycle. Coupled with breaking changes to the beta channel, this probably means that SDK 0.6 is probably due out soon.
On Fri, Aug 26, 2011 at 2:44 PM, Jeff Ward <j...@fuzzybinary.com> wrote: > I have a feeling (a chrome dev should probably confirm) that a new version > of 14 was pushed to beta channel that is now no longer supports the way we > were creating surfaces, and is instead using pp::Graphics3D_Dev.
> You may want to try adjusting your initialization code to match the new > tumbler sample and see if that fixes the issue.
> -- > Jeff
> On Fri, Aug 26, 2011 at 2:08 PM, Jamie Fristrom <jdfrist...@gmail.com>wrote:
>> Sorry, I failed to make clear just how weird what I'm seeing is. >> Everything was working and then it wasn't. I never updated the sdk - >> I'm still using 0_5_984. I'm not using the canary Chrome, I'm still >> using 14.0.835.109. And these aren't just my projects I'm having >> trouble with. The ogre3d and tumbler sample that Assaf put up, for >> example, load but don't render. They used to render for me, and then >> something just ... changed ... yesterday. >> (Assaf, do they still work for you? What version of Chrome are you >> using?) >> It's as if Chrome is just ignoring the --enable-accelerated-plugins >> command line parameter. >> Yes, I tried restarting my machine. I tried uninstalling and >> reinstalling chrome. I tried a couple of different ways of passing the >> command line to Chrome. I've only got one monitor. WebGL still works.
>> Sorry about this. If I were you I'd dismiss it as *some* kind of >> operator error, and I'm sure it is, I just don't know what, and don't >> really expect you to be able to help, but don't know what else to try >> at this point.
>> Any other ideas?
>> On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote: >> > I've been developing an opengl nacl thing fine for the past couple of >> > weeks - suddenly this afternoon the gl stopped working. Native Client >> > programs still run, but no graphics display, in the samples I've >> > looked at - including tumbler and ogre3d - so it isn't my code, it's >> > something changing in the browser...
>> > Things I've tried: >> > checked about:plugins and about:flags >> > checked my command line to make sure --enable-accelerated-plugins and >> > --enable-nacl are still there >> > checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV = >> > 1 >> > shutting down my computer and restarting it
>> > What could I be missing? What have I done to mess things up?
>> > Is it possible that chrome auto-updated to a different, not-working, >> > version? >> > About says it's 14.0.835.109 beta-m - I think that's the version I was >> > running before but am not positive.
>> -- >> You received this message because you are subscribed to the Google Groups >> "Native-Client-Discuss" group. >> To post to this group, send email to >> native-client-discuss@googlegroups.com. >> To unsubscribe from this group, send email to >> native-client-discuss+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/native-client-discuss?hl=en.
> I have a feeling (a chrome dev should probably confirm) that a new version
> of 14 was pushed to beta channel that is now no longer supports the way we
> were creating surfaces, and is instead using pp::Graphics3D_Dev.
> You may want to try adjusting your initialization code to match the new
> tumbler sample and see if that fixes the issue.
> --
> Jeff
> On Fri, Aug 26, 2011 at 2:08 PM, Jamie Fristrom <jdfrist...@gmail.com>wrote:
> > Sorry, I failed to make clear just how weird what I'm seeing is.
> > Everything was working and then it wasn't. I never updated the sdk -
> > I'm still using 0_5_984. I'm not using the canary Chrome, I'm still
> > using 14.0.835.109. And these aren't just my projects I'm having
> > trouble with. The ogre3d and tumbler sample that Assaf put up, for
> > example, load but don't render. They used to render for me, and then
> > something just ... changed ... yesterday.
> > (Assaf, do they still work for you? What version of Chrome are you
> > using?)
> > It's as if Chrome is just ignoring the --enable-accelerated-plugins
> > command line parameter.
> > Yes, I tried restarting my machine. I tried uninstalling and
> > reinstalling chrome. I tried a couple of different ways of passing the
> > command line to Chrome. I've only got one monitor. WebGL still works.
> > Sorry about this. If I were you I'd dismiss it as *some* kind of
> > operator error, and I'm sure it is, I just don't know what, and don't
> > really expect you to be able to help, but don't know what else to try
> > at this point.
> > Any other ideas?
> > On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote:
> > > I've been developing an opengl nacl thing fine for the past couple of
> > > weeks - suddenly this afternoon the gl stopped working. Native Client
> > > programs still run, but no graphics display, in the samples I've
> > > looked at - including tumbler and ogre3d - so it isn't my code, it's
> > > something changing in the browser...
> > > Things I've tried:
> > > checked about:plugins and about:flags
> > > checked my command line to make sure --enable-accelerated-plugins and
> > > --enable-nacl are still there
> > > checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV =
> > > 1
> > > shutting down my computer and restarting it
> > > What could I be missing? What have I done to mess things up?
> > > Is it possible that chrome auto-updated to a different, not-working,
> > > version?
> > > About says it's 14.0.835.109 beta-m - I think that's the version I was
> > > running before but am not positive.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Native-Client-Discuss" group.
> > To post to this group, send email to
> > native-client-discuss@googlegroups.com.
> > To unsubscribe from this group, send email to
> > native-client-discuss+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/native-client-discuss?hl=en.
> Could I have gotten a new version of Chrome without realizing it? Does > it happen automatically behind the scenes?
> On Aug 26, 11:44 am, Jeff Ward <j...@fuzzybinary.com> wrote: > > I have a feeling (a chrome dev should probably confirm) that a new > version > > of 14 was pushed to beta channel that is now no longer supports the way > we > > were creating surfaces, and is instead using pp::Graphics3D_Dev.
> > You may want to try adjusting your initialization code to match the new > > tumbler sample and see if that fixes the issue.
> > -- > > Jeff
> > On Fri, Aug 26, 2011 at 2:08 PM, Jamie Fristrom <jdfrist...@gmail.com > >wrote:
> > > Sorry, I failed to make clear just how weird what I'm seeing is. > > > Everything was working and then it wasn't. I never updated the sdk - > > > I'm still using 0_5_984. I'm not using the canary Chrome, I'm still > > > using 14.0.835.109. And these aren't just my projects I'm having > > > trouble with. The ogre3d and tumbler sample that Assaf put up, for > > > example, load but don't render. They used to render for me, and then > > > something just ... changed ... yesterday. > > > (Assaf, do they still work for you? What version of Chrome are you > > > using?) > > > It's as if Chrome is just ignoring the --enable-accelerated-plugins > > > command line parameter. > > > Yes, I tried restarting my machine. I tried uninstalling and > > > reinstalling chrome. I tried a couple of different ways of passing the > > > command line to Chrome. I've only got one monitor. WebGL still works.
> > > Sorry about this. If I were you I'd dismiss it as *some* kind of > > > operator error, and I'm sure it is, I just don't know what, and don't > > > really expect you to be able to help, but don't know what else to try > > > at this point.
> > > Any other ideas?
> > > On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote: > > > > I've been developing an opengl nacl thing fine for the past couple of > > > > weeks - suddenly this afternoon the gl stopped working. Native Client > > > > programs still run, but no graphics display, in the samples I've > > > > looked at - including tumbler and ogre3d - so it isn't my code, it's > > > > something changing in the browser...
> > > > Things I've tried: > > > > checked about:plugins and about:flags > > > > checked my command line to make sure --enable-accelerated-plugins and > > > > --enable-nacl are still there > > > > checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV = > > > > 1 > > > > shutting down my computer and restarting it
> > > > What could I be missing? What have I done to mess things up?
> > > > Is it possible that chrome auto-updated to a different, not-working, > > > > version? > > > > About says it's 14.0.835.109 beta-m - I think that's the version I > was > > > > running before but am not positive.
> > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Native-Client-Discuss" group. > > > To post to this group, send email to > > > native-client-discuss@googlegroups.com. > > > To unsubscribe from this group, send email to > > > native-client-discuss+unsubscribe@googlegroups.com. > > > For more options, visit this group at > > >http://groups.google.com/group/native-client-discuss?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Native-Client-Discuss" group. > To post to this group, send email to > native-client-discuss@googlegroups.com. > To unsubscribe from this group, send email to > native-client-discuss+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/native-client-discuss?hl=en.
Interesting. Does anyone know how to turn off that feature - so I can
get updates on my own schedule, when I'm ready? If it happens
automagically, I don't know if an introduced problem is something I
introduced or breaking changes in chrome.
On Aug 26, 12:34 pm, Jeff Ward <j...@fuzzybinary.com> wrote:
> In my experience, yes. Once you're in a channel, chrome will update
> itself automatically.
> On Fri, Aug 26, 2011 at 3:29 PM, Jamie Fristrom <jdfrist...@gmail.com>wrote:
> > Could I have gotten a new version of Chrome without realizing it? Does
> > it happen automatically behind the scenes?
> > On Aug 26, 11:44 am, Jeff Ward <j...@fuzzybinary.com> wrote:
> > > I have a feeling (a chrome dev should probably confirm) that a new
> > version
> > > of 14 was pushed to beta channel that is now no longer supports the way
> > we
> > > were creating surfaces, and is instead using pp::Graphics3D_Dev.
> > > You may want to try adjusting your initialization code to match the new
> > > tumbler sample and see if that fixes the issue.
> > > --
> > > Jeff
> > > On Fri, Aug 26, 2011 at 2:08 PM, Jamie Fristrom <jdfrist...@gmail.com
> > >wrote:
> > > > Sorry, I failed to make clear just how weird what I'm seeing is.
> > > > Everything was working and then it wasn't. I never updated the sdk -
> > > > I'm still using 0_5_984. I'm not using the canary Chrome, I'm still
> > > > using 14.0.835.109. And these aren't just my projects I'm having
> > > > trouble with. The ogre3d and tumbler sample that Assaf put up, for
> > > > example, load but don't render. They used to render for me, and then
> > > > something just ... changed ... yesterday.
> > > > (Assaf, do they still work for you? What version of Chrome are you
> > > > using?)
> > > > It's as if Chrome is just ignoring the --enable-accelerated-plugins
> > > > command line parameter.
> > > > Yes, I tried restarting my machine. I tried uninstalling and
> > > > reinstalling chrome. I tried a couple of different ways of passing the
> > > > command line to Chrome. I've only got one monitor. WebGL still works.
> > > > Sorry about this. If I were you I'd dismiss it as *some* kind of
> > > > operator error, and I'm sure it is, I just don't know what, and don't
> > > > really expect you to be able to help, but don't know what else to try
> > > > at this point.
> > > > Any other ideas?
> > > > On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote:
> > > > > I've been developing an opengl nacl thing fine for the past couple of
> > > > > weeks - suddenly this afternoon the gl stopped working. Native Client
> > > > > programs still run, but no graphics display, in the samples I've
> > > > > looked at - including tumbler and ogre3d - so it isn't my code, it's
> > > > > something changing in the browser...
> > > > > Things I've tried:
> > > > > checked about:plugins and about:flags
> > > > > checked my command line to make sure --enable-accelerated-plugins and
> > > > > --enable-nacl are still there
> > > > > checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV =
> > > > > 1
> > > > > shutting down my computer and restarting it
> > > > > What could I be missing? What have I done to mess things up?
> > > > > Is it possible that chrome auto-updated to a different, not-working,
> > > > > version?
> > > > > About says it's 14.0.835.109 beta-m - I think that's the version I
> > was
> > > > > running before but am not positive.
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "Native-Client-Discuss" group.
> > > > To post to this group, send email to
> > > > native-client-discuss@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > native-client-discuss+unsubscribe@googlegroups.com.
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/native-client-discuss?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Native-Client-Discuss" group.
> > To post to this group, send email to
> > native-client-discuss@googlegroups.com.
> > To unsubscribe from this group, send email to
> > native-client-discuss+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/native-client-discuss?hl=en.
It may not be that of a good idea to change Chrome in a way that you
can't write 3d NaCl programs without having a new Native Client SDK
that wasn't released yet.
My OGRE NaCl sample doesn't work - and in order to fix it I guess I
need to compile the NaCl SDK for windows on my own... I didn't plan
the time for it...
On the other hand - it seems that you are adding a 3d sample to the
next SDK release - so thanks for that!
Regards,
Assaf
On Aug 26, 9:47 pm, Jeff Ward <j...@fuzzybinary.com> wrote:
> By the way, although they probably can't confirm anything (they don't
> comment on schedule), I think the NaCL SDK team is on a 4-6 week release
> cycle. Coupled with breaking changes to the beta channel, this probably
> means that SDK 0.6 is probably due out soon.
> On Fri, Aug 26, 2011 at 2:44 PM, Jeff Ward <j...@fuzzybinary.com> wrote:
> > I have a feeling (a chrome dev should probably confirm) that a new version
> > of 14 was pushed to beta channel that is now no longer supports the way we
> > were creating surfaces, and is instead using pp::Graphics3D_Dev.
> > You may want to try adjusting your initialization code to match the new
> > tumbler sample and see if that fixes the issue.
> > --
> > Jeff
> > On Fri, Aug 26, 2011 at 2:08 PM, Jamie Fristrom <jdfrist...@gmail.com>wrote:
> >> Sorry, I failed to make clear just how weird what I'm seeing is.
> >> Everything was working and then it wasn't. I never updated the sdk -
> >> I'm still using 0_5_984. I'm not using the canary Chrome, I'm still
> >> using 14.0.835.109. And these aren't just my projects I'm having
> >> trouble with. The ogre3d and tumbler sample that Assaf put up, for
> >> example, load but don't render. They used to render for me, and then
> >> something just ... changed ... yesterday.
> >> (Assaf, do they still work for you? What version of Chrome are you
> >> using?)
> >> It's as if Chrome is just ignoring the --enable-accelerated-plugins
> >> command line parameter.
> >> Yes, I tried restarting my machine. I tried uninstalling and
> >> reinstalling chrome. I tried a couple of different ways of passing the
> >> command line to Chrome. I've only got one monitor. WebGL still works.
> >> Sorry about this. If I were you I'd dismiss it as *some* kind of
> >> operator error, and I'm sure it is, I just don't know what, and don't
> >> really expect you to be able to help, but don't know what else to try
> >> at this point.
> >> Any other ideas?
> >> On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote:
> >> > I've been developing an opengl nacl thing fine for the past couple of
> >> > weeks - suddenly this afternoon the gl stopped working. Native Client
> >> > programs still run, but no graphics display, in the samples I've
> >> > looked at - including tumbler and ogre3d - so it isn't my code, it's
> >> > something changing in the browser...
> >> > Things I've tried:
> >> > checked about:plugins and about:flags
> >> > checked my command line to make sure --enable-accelerated-plugins and
> >> > --enable-nacl are still there
> >> > checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV =
> >> > 1
> >> > shutting down my computer and restarting it
> >> > What could I be missing? What have I done to mess things up?
> >> > Is it possible that chrome auto-updated to a different, not-working,
> >> > version?
> >> > About says it's 14.0.835.109 beta-m - I think that's the version I was
> >> > running before but am not positive.
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "Native-Client-Discuss" group.
> >> To post to this group, send email to
> >> native-client-discuss@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> native-client-discuss+unsubscribe@googlegroups.com.
> >> For more options, visit this group at
> >>http://groups.google.com/group/native-client-discuss?hl=en.
One other note, you write here: http://code.google.com/chrome/nativeclient/docs/releasenotes.html#0.5 "
Starting with Chrome 14, Native Client has a stable application binary
interface (ABI). That means there is no longer a need to match
versions of Chrome with versions of the SDK. Applications compiled
with version 0.5 of the SDK will work in Chrome 14 and future versions
of Chrome.
"
I guess I didn't understand, but I have an nexe that was compiled with
0.5 that doesn't work in Chrome 14... I can even make changes in my
code and recompile it so it works.
You may want to clarify that in the 0.6 SDK release notes...
Regards,
Assaf
On Aug 26, 11:45 pm, Assaf Raman <assafra...@gmail.com> wrote:
> It may not be that of a good idea to change Chrome in a way that you
> can't write 3d NaCl programs without having a new Native Client SDK
> that wasn't released yet.
> My OGRE NaCl sample doesn't work - and in order to fix it I guess I
> need to compile the NaCl SDK for windows on my own... I didn't plan
> the time for it...
> On the other hand - it seems that you are adding a 3d sample to the
> next SDK release - so thanks for that!
> Regards,
> Assaf
> On Aug 26, 9:47 pm, Jeff Ward <j...@fuzzybinary.com> wrote:
> > By the way, although they probably can't confirm anything (they don't
> > comment on schedule), I think the NaCL SDK team is on a 4-6 week release
> > cycle. Coupled with breaking changes to the beta channel, this probably
> > means that SDK 0.6 is probably due out soon.
> > On Fri, Aug 26, 2011 at 2:44 PM, Jeff Ward <j...@fuzzybinary.com> wrote:
> > > I have a feeling (a chrome dev should probably confirm) that a new version
> > > of 14 was pushed to beta channel that is now no longer supports the way we
> > > were creating surfaces, and is instead using pp::Graphics3D_Dev.
> > > You may want to try adjusting your initialization code to match the new
> > > tumbler sample and see if that fixes the issue.
> > > --
> > > Jeff
> > > On Fri, Aug 26, 2011 at 2:08 PM, Jamie Fristrom <jdfrist...@gmail.com>wrote:
> > >> Sorry, I failed to make clear just how weird what I'm seeing is.
> > >> Everything was working and then it wasn't. I never updated the sdk -
> > >> I'm still using 0_5_984. I'm not using the canary Chrome, I'm still
> > >> using 14.0.835.109. And these aren't just my projects I'm having
> > >> trouble with. The ogre3d and tumbler sample that Assaf put up, for
> > >> example, load but don't render. They used to render for me, and then
> > >> something just ... changed ... yesterday.
> > >> (Assaf, do they still work for you? What version of Chrome are you
> > >> using?)
> > >> It's as if Chrome is just ignoring the --enable-accelerated-plugins
> > >> command line parameter.
> > >> Yes, I tried restarting my machine. I tried uninstalling and
> > >> reinstalling chrome. I tried a couple of different ways of passing the
> > >> command line to Chrome. I've only got one monitor. WebGL still works.
> > >> Sorry about this. If I were you I'd dismiss it as *some* kind of
> > >> operator error, and I'm sure it is, I just don't know what, and don't
> > >> really expect you to be able to help, but don't know what else to try
> > >> at this point.
> > >> Any other ideas?
> > >> On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote:
> > >> > I've been developing an opengl nacl thing fine for the past couple of
> > >> > weeks - suddenly this afternoon the gl stopped working. Native Client
> > >> > programs still run, but no graphics display, in the samples I've
> > >> > looked at - including tumbler and ogre3d - so it isn't my code, it's
> > >> > something changing in the browser...
> > >> > Things I've tried:
> > >> > checked about:plugins and about:flags
> > >> > checked my command line to make sure --enable-accelerated-plugins and
> > >> > --enable-nacl are still there
> > >> > checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV =
> > >> > 1
> > >> > shutting down my computer and restarting it
> > >> > What could I be missing? What have I done to mess things up?
> > >> > Is it possible that chrome auto-updated to a different, not-working,
> > >> > version?
> > >> > About says it's 14.0.835.109 beta-m - I think that's the version I was
> > >> > running before but am not positive.
> > >> --
> > >> You received this message because you are subscribed to the Google Groups
> > >> "Native-Client-Discuss" group.
> > >> To post to this group, send email to
> > >> native-client-discuss@googlegroups.com.
> > >> To unsubscribe from this group, send email to
> > >> native-client-discuss+unsubscribe@googlegroups.com.
> > >> For more options, visit this group at
> > >>http://groups.google.com/group/native-client-discuss?hl=en.
> One other note, you write here:http://code.google.com/chrome/nativeclient/docs/releasenotes.html#0.5 > "
> Starting with Chrome 14, Native Client has a stable application binary
> interface (ABI). That means there is no longer a need to match
> versions of Chrome with versions of the SDK. Applications compiled
> with version 0.5 of the SDK will work in Chrome 14 and future versions
> of Chrome.
> "
> I guess I didn't understand, but I have an nexe that was compiled with
> 0.5 that doesn't work in Chrome 14... I can even make changes in my
> code and recompile it so it works.
> You may want to clarify that in the 0.6 SDK release notes...
> Regards,
> Assaf
> On Aug 26, 11:45 pm, Assaf Raman <assafra...@gmail.com> wrote:
> > Hi,
> > It may not be that of a good idea to change Chrome in a way that you
> > can't write 3d NaCl programs without having a new Native Client SDK
> > that wasn't released yet.
> > My OGRE NaCl sample doesn't work - and in order to fix it I guess I
> > need to compile the NaCl SDK for windows on my own... I didn't plan
> > the time for it...
> > On the other hand - it seems that you are adding a 3d sample to the
> > next SDK release - so thanks for that!
> > Regards,
> > Assaf
> > On Aug 26, 9:47 pm, Jeff Ward <j...@fuzzybinary.com> wrote:
> > > By the way, although they probably can't confirm anything (they don't
> > > comment on schedule), I think the NaCL SDK team is on a 4-6 week release
> > > cycle. Coupled with breaking changes to the beta channel, this probably
> > > means that SDK 0.6 is probably due out soon.
> > > On Fri, Aug 26, 2011 at 2:44 PM, Jeff Ward <j...@fuzzybinary.com> wrote:
> > > > I have a feeling (a chrome dev should probably confirm) that a new version
> > > > of 14 was pushed to beta channel that is now no longer supports the way we
> > > > were creating surfaces, and is instead using pp::Graphics3D_Dev.
> > > > You may want to try adjusting your initialization code to match the new
> > > > tumbler sample and see if that fixes the issue.
> > > > --
> > > > Jeff
> > > > On Fri, Aug 26, 2011 at 2:08 PM, Jamie Fristrom <jdfrist...@gmail.com>wrote:
> > > >> Sorry, I failed to make clear just how weird what I'm seeing is.
> > > >> Everything was working and then it wasn't. I never updated the sdk -
> > > >> I'm still using 0_5_984. I'm not using the canary Chrome, I'm still
> > > >> using 14.0.835.109. And these aren't just my projects I'm having
> > > >> trouble with. The ogre3d and tumbler sample that Assaf put up, for
> > > >> example, load but don't render. They used to render for me, and then
> > > >> something just ... changed ... yesterday.
> > > >> (Assaf, do they still work for you? What version of Chrome are you
> > > >> using?)
> > > >> It's as if Chrome is just ignoring the --enable-accelerated-plugins
> > > >> command line parameter.
> > > >> Yes, I tried restarting my machine. I tried uninstalling and
> > > >> reinstalling chrome. I tried a couple of different ways of passing the
> > > >> command line to Chrome. I've only got one monitor. WebGL still works.
> > > >> Sorry about this. If I were you I'd dismiss it as *some* kind of
> > > >> operator error, and I'm sure it is, I just don't know what, and don't
> > > >> really expect you to be able to help, but don't know what else to try
> > > >> at this point.
> > > >> Any other ideas?
> > > >> On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote:
> > > >> > I've been developing an opengl nacl thing fine for the past couple of
> > > >> > weeks - suddenly this afternoon the gl stopped working. Native Client
> > > >> > programs still run, but no graphics display, in the samples I've
> > > >> > looked at - including tumbler and ogre3d - so it isn't my code, it's
> > > >> > something changing in the browser...
> > > >> > Things I've tried:
> > > >> > checked about:plugins and about:flags
> > > >> > checked my command line to make sure --enable-accelerated-plugins and
> > > >> > --enable-nacl are still there
> > > >> > checked my environment variables to make sure NACL_ENABLE_PPAPI_DEV =
> > > >> > 1
> > > >> > shutting down my computer and restarting it
> > > >> > What could I be missing? What have I done to mess things up?
> > > >> > Is it possible that chrome auto-updated to a different, not-working,
> > > >> > version?
> > > >> > About says it's 14.0.835.109 beta-m - I think that's the version I was
> > > >> > running before but am not positive.
> > > >> --
> > > >> You received this message because you are subscribed to the Google Groups
> > > >> "Native-Client-Discuss" group.
> > > >> To post to this group, send email to
> > > >> native-client-discuss@googlegroups.com.
> > > >> To unsubscribe from this group, send email to
> > > >> native-client-discuss+unsubscribe@googlegroups.com.
> > > >> For more options, visit this group at
> > > >>http://groups.google.com/group/native-client-discuss?hl=en.
On Fri, Aug 26, 2011 at 3:03 PM, Assaf Raman <assafra...@gmail.com> wrote: > Typo - it should have been: I can't even make changes in my code and > recompile it so it works.
Folks: just to be clear, as of Chrome M14 3D is an unsupported API in Pepper, as are all APIs with the _Dev suffix. This means there are no guarantees that your code will run or even compile between versions of Chrome.
Once 3D reaches the stable channel (it is promoted from _Dev), then it will be guaranteed to work. Until then, all bets are off.
Perhaps this fact could be explained a little more clearly in the NaCl SDK docs?
> On Aug 27, 12:01 am, Assaf Raman <assafra...@gmail.com> wrote: > > Hi,
> > One other note, you write here: > http://code.google.com/chrome/nativeclient/docs/releasenotes.html#0.5 > > " > > Starting with Chrome 14, Native Client has a stable application binary > > interface (ABI). That means there is no longer a need to match > > versions of Chrome with versions of the SDK. Applications compiled > > with version 0.5 of the SDK will work in Chrome 14 and future versions > > of Chrome. > > "
> > I guess I didn't understand, but I have an nexe that was compiled with > > 0.5 that doesn't work in Chrome 14... I can even make changes in my > > code and recompile it so it works. > > You may want to clarify that in the 0.6 SDK release notes...
> > Regards,
> > Assaf
> > On Aug 26, 11:45 pm, Assaf Raman <assafra...@gmail.com> wrote:
> > > Hi,
> > > It may not be that of a good idea to change Chrome in a way that you > > > can't write 3d NaCl programs without having a new Native Client SDK > > > that wasn't released yet.
> > > My OGRE NaCl sample doesn't work - and in order to fix it I guess I > > > need to compile the NaCl SDK for windows on my own... I didn't plan > > > the time for it...
> > > On the other hand - it seems that you are adding a 3d sample to the > > > next SDK release - so thanks for that!
> > > Regards,
> > > Assaf
> > > On Aug 26, 9:47 pm, Jeff Ward <j...@fuzzybinary.com> wrote:
> > > > By the way, although they probably can't confirm anything (they don't > > > > comment on schedule), I think the NaCL SDK team is on a 4-6 week > release > > > > cycle. Coupled with breaking changes to the beta channel, this > probably > > > > means that SDK 0.6 is probably due out soon.
> > > > On Fri, Aug 26, 2011 at 2:44 PM, Jeff Ward <j...@fuzzybinary.com> > wrote: > > > > > I have a feeling (a chrome dev should probably confirm) that a new > version > > > > > of 14 was pushed to beta channel that is now no longer supports the > way we > > > > > were creating surfaces, and is instead using pp::Graphics3D_Dev.
> > > > > If you look at the tumber sample that's currently in source control > (
> > > > > You may want to try adjusting your initialization code to match the > new > > > > > tumbler sample and see if that fixes the issue.
> > > > > -- > > > > > Jeff
> > > > > On Fri, Aug 26, 2011 at 2:08 PM, Jamie Fristrom < > jdfrist...@gmail.com>wrote:
> > > > >> Sorry, I failed to make clear just how weird what I'm seeing is. > > > > >> Everything was working and then it wasn't. I never updated the sdk > - > > > > >> I'm still using 0_5_984. I'm not using the canary Chrome, I'm > still > > > > >> using 14.0.835.109. And these aren't just my projects I'm having > > > > >> trouble with. The ogre3d and tumbler sample that Assaf put up, for > > > > >> example, load but don't render. They used to render for me, and > then > > > > >> something just ... changed ... yesterday. > > > > >> (Assaf, do they still work for you? What version of Chrome are you > > > > >> using?) > > > > >> It's as if Chrome is just ignoring the > --enable-accelerated-plugins > > > > >> command line parameter. > > > > >> Yes, I tried restarting my machine. I tried uninstalling and > > > > >> reinstalling chrome. I tried a couple of different ways of passing > the > > > > >> command line to Chrome. I've only got one monitor. WebGL still > works.
> > > > >> Sorry about this. If I were you I'd dismiss it as *some* kind of > > > > >> operator error, and I'm sure it is, I just don't know what, and > don't > > > > >> really expect you to be able to help, but don't know what else to > try > > > > >> at this point.
> > > > >> Any other ideas?
> > > > >> On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote: > > > > >> > I've been developing an opengl nacl thing fine for the past > couple of > > > > >> > weeks - suddenly this afternoon the gl stopped working. Native > Client > > > > >> > programs still run, but no graphics display, in the samples I've > > > > >> > looked at - including tumbler and ogre3d - so it isn't my code, > it's > > > > >> > something changing in the browser...
> > > > >> > Things I've tried: > > > > >> > checked about:plugins and about:flags > > > > >> > checked my command line to make sure > --enable-accelerated-plugins and > > > > >> > --enable-nacl are still there > > > > >> > checked my environment variables to make sure > NACL_ENABLE_PPAPI_DEV = > > > > >> > 1 > > > > >> > shutting down my computer and restarting it
> > > > >> > What could I be missing? What have I done to mess things up?
> > > > >> > Is it possible that chrome auto-updated to a different, > not-working, > > > > >> > version? > > > > >> > About says it's 14.0.835.109 beta-m - I think that's the version > I was > > > > >> > running before but am not positive.
> > > > >> -- > > > > >> You received this message because you are subscribed to the Google > Groups > > > > >> "Native-Client-Discuss" group. > > > > >> To post to this group, send email to > > > > >> native-client-discuss@googlegroups.com. > > > > >> To unsubscribe from this group, send email to > > > > >> native-client-discuss+unsubscribe@googlegroups.com. > > > > >> For more options, visit this group at > > > > >>http://groups.google.com/group/native-client-discuss?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Native-Client-Discuss" group. > To post to this group, send email to > native-client-discuss@googlegroups.com. > To unsubscribe from this group, send email to > native-client-discuss+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/native-client-discuss?hl=en.
This refers to the ABI, the binary interface, not the API. In previous versions of the SDK / Chrome, a compiled .nexe wouldn't even load in a mismatched version of Chrome. Here, the nexe is loading and running, but the API it's using is unstable.
On Fri, Aug 26, 2011 at 5:03 PM, Assaf Raman <assafra...@gmail.com> wrote: > Typo - it should have been: I can't even make changes in my code and > recompile it so it works.
> On Aug 27, 12:01 am, Assaf Raman <assafra...@gmail.com> wrote: > > Hi,
> > One other note, you write here: > http://code.google.com/chrome/nativeclient/docs/releasenotes.html#0.5 > > " > > Starting with Chrome 14, Native Client has a stable application binary > > interface (ABI). That means there is no longer a need to match > > versions of Chrome with versions of the SDK. Applications compiled > > with version 0.5 of the SDK will work in Chrome 14 and future versions > > of Chrome. > > "
> > I guess I didn't understand, but I have an nexe that was compiled with > > 0.5 that doesn't work in Chrome 14... I can even make changes in my > > code and recompile it so it works. > > You may want to clarify that in the 0.6 SDK release notes...
> > Regards,
> > Assaf
> > On Aug 26, 11:45 pm, Assaf Raman <assafra...@gmail.com> wrote:
> > > Hi,
> > > It may not be that of a good idea to change Chrome in a way that you > > > can't write 3d NaCl programs without having a new Native Client SDK > > > that wasn't released yet.
> > > My OGRE NaCl sample doesn't work - and in order to fix it I guess I > > > need to compile the NaCl SDK for windows on my own... I didn't plan > > > the time for it...
> > > On the other hand - it seems that you are adding a 3d sample to the > > > next SDK release - so thanks for that!
> > > Regards,
> > > Assaf
> > > On Aug 26, 9:47 pm, Jeff Ward <j...@fuzzybinary.com> wrote:
> > > > By the way, although they probably can't confirm anything (they don't > > > > comment on schedule), I think the NaCL SDK team is on a 4-6 week > release > > > > cycle. Coupled with breaking changes to the beta channel, this > probably > > > > means that SDK 0.6 is probably due out soon.
> > > > On Fri, Aug 26, 2011 at 2:44 PM, Jeff Ward <j...@fuzzybinary.com> > wrote: > > > > > I have a feeling (a chrome dev should probably confirm) that a new > version > > > > > of 14 was pushed to beta channel that is now no longer supports the > way we > > > > > were creating surfaces, and is instead using pp::Graphics3D_Dev.
> > > > > If you look at the tumber sample that's currently in source control > (
> > > > > You may want to try adjusting your initialization code to match the > new > > > > > tumbler sample and see if that fixes the issue.
> > > > > -- > > > > > Jeff
> > > > > On Fri, Aug 26, 2011 at 2:08 PM, Jamie Fristrom < > jdfrist...@gmail.com>wrote:
> > > > >> Sorry, I failed to make clear just how weird what I'm seeing is. > > > > >> Everything was working and then it wasn't. I never updated the sdk > - > > > > >> I'm still using 0_5_984. I'm not using the canary Chrome, I'm > still > > > > >> using 14.0.835.109. And these aren't just my projects I'm having > > > > >> trouble with. The ogre3d and tumbler sample that Assaf put up, for > > > > >> example, load but don't render. They used to render for me, and > then > > > > >> something just ... changed ... yesterday. > > > > >> (Assaf, do they still work for you? What version of Chrome are you > > > > >> using?) > > > > >> It's as if Chrome is just ignoring the > --enable-accelerated-plugins > > > > >> command line parameter. > > > > >> Yes, I tried restarting my machine. I tried uninstalling and > > > > >> reinstalling chrome. I tried a couple of different ways of passing > the > > > > >> command line to Chrome. I've only got one monitor. WebGL still > works.
> > > > >> Sorry about this. If I were you I'd dismiss it as *some* kind of > > > > >> operator error, and I'm sure it is, I just don't know what, and > don't > > > > >> really expect you to be able to help, but don't know what else to > try > > > > >> at this point.
> > > > >> Any other ideas?
> > > > >> On Aug 25, 5:10 pm, Jamie Fristrom <jdfrist...@gmail.com> wrote: > > > > >> > I've been developing an opengl nacl thing fine for the past > couple of > > > > >> > weeks - suddenly this afternoon the gl stopped working. Native > Client > > > > >> > programs still run, but no graphics display, in the samples I've > > > > >> > looked at - including tumbler and ogre3d - so it isn't my code, > it's > > > > >> > something changing in the browser...
> > > > >> > Things I've tried: > > > > >> > checked about:plugins and about:flags > > > > >> > checked my command line to make sure > --enable-accelerated-plugins and > > > > >> > --enable-nacl are still there > > > > >> > checked my environment variables to make sure > NACL_ENABLE_PPAPI_DEV = > > > > >> > 1 > > > > >> > shutting down my computer and restarting it
> > > > >> > What could I be missing? What have I done to mess things up?
> > > > >> > Is it possible that chrome auto-updated to a different, > not-working, > > > > >> > version? > > > > >> > About says it's 14.0.835.109 beta-m - I think that's the version > I was > > > > >> > running before but am not positive.
> > > > >> -- > > > > >> You received this message because you are subscribed to the Google > Groups > > > > >> "Native-Client-Discuss" group. > > > > >> To post to this group, send email to > > > > >> native-client-discuss@googlegroups.com. > > > > >> To unsubscribe from this group, send email to > > > > >> native-client-discuss+unsubscribe@googlegroups.com. > > > > >> For more options, visit this group at > > > > >>http://groups.google.com/group/native-client-discuss?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Native-Client-Discuss" group. > To post to this group, send email to > native-client-discuss@googlegroups.com. > To unsubscribe from this group, send email to > native-client-discuss+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/native-client-discuss?hl=en.
On Sat, Aug 27, 2011 at 1:23 AM, Jeff Ward <j...@fuzzybinary.com> wrote: > Assaf,
> This refers to the ABI, the binary interface, not the API. In previous > versions of the SDK / Chrome, a compiled .nexe wouldn't even load in a > mismatched version of Chrome. Here, the nexe is loading and running, but > the API it's using is unstable.
> Well, it refers to ABI, but this is not the problem. The problem is that
you've used _Dev interface. When you did that you forfeited support: these interfaces can be broken at any time without any warnings. Once they are stabilized _Dev prefix is removed and you can use them safely. This is how Extensions API is changing over time in Chrome, so it's not a new model.
Perhaps this should be noted prominently in release notes...
I think everyone understands we're using a _Dev interface. I think the problem for Jamie and Assaf are having is that the _Dev interface broke completely silently in a minor Chrome update. I don't think anyone is ready to publish anything here (I could be wrong, but that's my understanding), but we do like our development environments to be stable while we're tinkering.
Generally, I think we're all prepared for _Dev interfaces to break, but having control over *when* they break is usually nice (meaning, when we explicitly update Chrome, instead of when it silently updates). At least then we can narrow down the problem to the update.
Anyway, the original question was just "Did chrome update itself and break OpenGL support?" The simple answer is "Yes. Yes it did."
The next question is "Can we disable Chrome automatic updates?"
Then of course, the inevitable "Is that a good idea?" ;)
On Fri, Aug 26, 2011 at 5:26 PM, Victor Khimenko <k...@google.com> wrote:
> On Sat, Aug 27, 2011 at 1:23 AM, Jeff Ward <j...@fuzzybinary.com> wrote:
>> Assaf,
>> This refers to the ABI, the binary interface, not the API. In previous >> versions of the SDK / Chrome, a compiled .nexe wouldn't even load in a >> mismatched version of Chrome. Here, the nexe is loading and running, but >> the API it's using is unstable.
>> Well, it refers to ABI, but this is not the problem. The problem is that > you've used _Dev interface. When you did that you forfeited support: these > interfaces can be broken at any time without any warnings. Once they are > stabilized _Dev prefix is removed and you can use them safely. This is how > Extensions API is changing over time in Chrome, so it's not a new model.
> Perhaps this should be noted prominently in release notes...
> -- > You received this message because you are subscribed to the Google Groups > "Native-Client-Discuss" group. > To post to this group, send email to > native-client-discuss@googlegroups.com. > To unsubscribe from this group, send email to > native-client-discuss+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/native-client-discuss?hl=en.
I understand.
I disabled all my demo pages and added a note about this issue - until
it is resolved.
Note that you have links to my OGRE NaCl demo in some of your issues.
I will update the demos soon after you will release the next SDK (0.6)
- and re-enable the pages.
Keep up the good work, as I wrote - moving 3d to be a stable feature
is something all of us in the OGRE community wait for.
I even have the code for the first NaCl OGRE 3d game that will be in
the app store (a GPL 3d chess).
Cheers,
Assaf
On Aug 27, 12:26 am, Victor Khimenko <k...@google.com> wrote:
> On Sat, Aug 27, 2011 at 1:23 AM, Jeff Ward <j...@fuzzybinary.com> wrote:
> > Assaf,
> > This refers to the ABI, the binary interface, not the API. In previous
> > versions of the SDK / Chrome, a compiled .nexe wouldn't even load in a
> > mismatched version of Chrome. Here, the nexe is loading and running, but
> > the API it's using is unstable.
> > Well, it refers to ABI, but this is not the problem. The problem is that
> you've used _Dev interface. When you did that you forfeited support: these
> interfaces can be broken at any time without any warnings. Once they are
> stabilized _Dev prefix is removed and you can use them safely. This is how
> Extensions API is changing over time in Chrome, so it's not a new model.
> Perhaps this should be noted prominently in release notes...
I don't know how to stop the autoupdate of Canary/Chrome, but it would be a nice feature. And it would be awesome to have an about:versions page where you could see the latest history of upgrades/versions..
Thanks, everybody, for trying out the cutting edge Chrome and for reporting the issues!
As others have mentioned, sporadic breakages are likely to occur while the 3D interfaces are in dev/. Chrome auto-updates itself when a newer version is available on the given channel (stable, beta, dev, or canary), and it is not possible to turn this off. To avoid potential breakage when this happens, you can use known good versions of Chromium, Chrome's non-Google branded sibling, which does not auto-update itself. You can find Chromium builds at http://commondatastorage.googleapis.com/chromium-browser-continuous/i... .
Known good builds of Chromium include revisions 96198 and 97282 (using pp::Surface3D_Dev and pp::Context3D_Dev) and revision 98412 (using the newer pp::Graphics3D_Dev). If you are using the currently released SDK, you should use one of the former; if you feel adventurous and don't mind checking stuff out from our repositories, you can use the latter.
ABI stability means that a nexe will continue to work from the first version where all the interfaces it uses were out of dev/ and onwards. It does not mean the APIs won't change in newer versions (potentially necessitating adjustments when recompiling).
We are working on getting the 3D interfaces stabilized, so that we can pull them out of dev/. When that happens you will be able to use Chrome for development purposes. Coming interfaces such as full-screen, mouse lock, peer-to-peer networking, and Web Sockets will go through the same process: early adopters who are keen to get started may want to use known good builds of Chromium to shield themselves from the churn until the interfaces are out of dev/.
On Fri, Aug 26, 2011 at 2:39 PM, Assaf Raman <assafra...@gmail.com> wrote: > I understand. > I disabled all my demo pages and added a note about this issue - until > it is resolved. > Note that you have links to my OGRE NaCl demo in some of your issues. > I will update the demos soon after you will release the next SDK (0.6) > - and re-enable the pages. > Keep up the good work, as I wrote - moving 3d to be a stable feature > is something all of us in the OGRE community wait for. > I even have the code for the first NaCl OGRE 3d game that will be in > the app store (a GPL 3d chess).
> Cheers,
> Assaf
> On Aug 27, 12:26 am, Victor Khimenko <k...@google.com> wrote: > > On Sat, Aug 27, 2011 at 1:23 AM, Jeff Ward <j...@fuzzybinary.com> wrote: > > > Assaf,
> > > This refers to the ABI, the binary interface, not the API. In previous > > > versions of the SDK / Chrome, a compiled .nexe wouldn't even load in a > > > mismatched version of Chrome. Here, the nexe is loading and running, > but > > > the API it's using is unstable.
> > > Well, it refers to ABI, but this is not the problem. The problem is > that
> > you've used _Dev interface. When you did that you forfeited support: > these > > interfaces can be broken at any time without any warnings. Once they are > > stabilized _Dev prefix is removed and you can use them safely. This is > how > > Extensions API is changing over time in Chrome, so it's not a new model.
> > Perhaps this should be noted prominently in release notes...
> -- > You received this message because you are subscribed to the Google Groups > "Native-Client-Discuss" group. > To post to this group, send email to > native-client-discuss@googlegroups.com. > To unsubscribe from this group, send email to > native-client-discuss+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/native-client-discuss?hl=en.
Thanks so much - yes, switching to the Chromium build fixed it (I went
for 97282 - I'm not *that* adventurous). Good to know I'm not crazy.
And Jeff for president, he said exactly what I was trying to say.
On Aug 26, 3:31 pm, Christian Stefansen <cstefan...@google.com> wrote:
> Thanks, everybody, for trying out the cutting edge Chrome and for reporting
> the issues!
> As others have mentioned, sporadic breakages are likely to occur while the
> 3D interfaces are in dev/. Chrome auto-updates itself when a newer version
> is available on the given channel (stable, beta, dev, or canary), and it is
> not possible to turn this off. To avoid potential breakage when this
> happens, you can use known good versions of Chromium, Chrome's non-Google
> branded sibling, which does not auto-update itself. You can find Chromium
> builds athttp://commondatastorage.googleapis.com/chromium-browser-continuous/i...
> .
> Known good builds of Chromium include revisions 96198 and 97282 (using
> pp::Surface3D_Dev and pp::Context3D_Dev) and revision 98412 (using the newer
> pp::Graphics3D_Dev). If you are using the currently released SDK, you should
> use one of the former; if you feel adventurous and don't mind checking stuff
> out from our repositories, you can use the latter.
> ABI stability means that a nexe will continue to work from the first version
> where all the interfaces it uses were out of dev/ and onwards. It does not
> mean the APIs won't change in newer versions (potentially necessitating
> adjustments when recompiling).
> We are working on getting the 3D interfaces stabilized, so that we can pull
> them out of dev/. When that happens you will be able to use Chrome for
> development purposes. Coming interfaces such as full-screen, mouse lock,
> peer-to-peer networking, and Web Sockets will go through the same process:
> early adopters who are keen to get started may want to use known good builds
> of Chromium to shield themselves from the churn until the interfaces are out
> of dev/.
> Cheers,
> Christian
> On Fri, Aug 26, 2011 at 2:39 PM, Assaf Raman <assafra...@gmail.com> wrote:
> > I understand.
> > I disabled all my demo pages and added a note about this issue - until
> > it is resolved.
> > Note that you have links to my OGRE NaCl demo in some of your issues.
> > I will update the demos soon after you will release the next SDK (0.6)
> > - and re-enable the pages.
> > Keep up the good work, as I wrote - moving 3d to be a stable feature
> > is something all of us in the OGRE community wait for.
> > I even have the code for the first NaCl OGRE 3d game that will be in
> > the app store (a GPL 3d chess).
> > Cheers,
> > Assaf
> > On Aug 27, 12:26 am, Victor Khimenko <k...@google.com> wrote:
> > > On Sat, Aug 27, 2011 at 1:23 AM, Jeff Ward <j...@fuzzybinary.com> wrote:
> > > > Assaf,
> > > > This refers to the ABI, the binary interface, not the API. In previous
> > > > versions of the SDK / Chrome, a compiled .nexe wouldn't even load in a
> > > > mismatched version of Chrome. Here, the nexe is loading and running,
> > but
> > > > the API it's using is unstable.
> > > > Well, it refers to ABI, but this is not the problem. The problem is
> > that
> > > you've used _Dev interface. When you did that you forfeited support:
> > these
> > > interfaces can be broken at any time without any warnings. Once they are
> > > stabilized _Dev prefix is removed and you can use them safely. This is
> > how
> > > Extensions API is changing over time in Chrome, so it's not a new model.
> > > Perhaps this should be noted prominently in release notes...
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Native-Client-Discuss" group.
> > To post to this group, send email to
> > native-client-discuss@googlegroups.com.
> > To unsubscribe from this group, send email to
> > native-client-discuss+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/native-client-discuss?hl=en.
> --
> Christian Stefansen
> Product Manager
> Google
I got the latest? SDK (0.5.1052) and tried to create a little GL app
(compiles/links fine), but running it in build 98412 fails because
glInitializePPAPI(..) in the module Init() method is returning false.
I also tried 97282 and 15.0.865.0 canary and found the same issue. FYI
- the module runs fine, but glInitializePPAPI() is returning false.
Does anyone else have this problem? Anyone have a list of cases where
the call may fail?
Thanks!
Prasad
On Aug 26, 6:31 pm, Christian Stefansen <cstefan...@google.com> wrote:
> Thanks, everybody, for trying out the cutting edge Chrome and for reporting
> the issues!
> As others have mentioned, sporadic breakages are likely to occur while the
> 3D interfaces are in dev/. Chrome auto-updates itself when a newer version
> is available on the given channel (stable, beta, dev, or canary), and it is
> not possible to turn this off. To avoid potential breakage when this
> happens, you can use known good versions of Chromium, Chrome's non-Google
> branded sibling, which does not auto-update itself. You can find Chromium
> builds athttp://commondatastorage.googleapis.com/chromium-browser-continuous/i...
> .
> Known good builds of Chromium include revisions 96198 and 97282 (using
> pp::Surface3D_Dev and pp::Context3D_Dev) and revision 98412 (using the newer
> pp::Graphics3D_Dev). If you are using the currently released SDK, you should
> use one of the former; if you feel adventurous and don't mind checking stuff
> out from our repositories, you can use the latter.
> ABI stability means that a nexe will continue to work from the first version
> where all the interfaces it uses were out of dev/ and onwards. It does not
> mean the APIs won't change in newer versions (potentially necessitating
> adjustments when recompiling).
> We are working on getting the 3D interfaces stabilized, so that we can pull
> them out of dev/. When that happens you will be able to use Chrome for
> development purposes. Coming interfaces such as full-screen, mouse lock,
> peer-to-peer networking, and Web Sockets will go through the same process:
> early adopters who are keen to get started may want to use known good builds
> of Chromium to shield themselves from the churn until the interfaces are out
> of dev/.
> Cheers,
> Christian
> On Fri, Aug 26, 2011 at 2:39 PM, Assaf Raman <assafra...@gmail.com> wrote:
> > I understand.
> > I disabled all my demo pages and added a note about this issue - until
> > it is resolved.
> > Note that you have links to my OGRE NaCl demo in some of your issues.
> > I will update the demos soon after you will release the next SDK (0.6)
> > - and re-enable the pages.
> > Keep up the good work, as I wrote - moving 3d to be a stable feature
> > is something all of us in the OGRE community wait for.
> > I even have the code for the first NaCl OGRE 3d game that will be in
> > the app store (a GPL 3d chess).
> > Cheers,
> > Assaf
> > On Aug 27, 12:26 am, Victor Khimenko <k...@google.com> wrote:
> > > On Sat, Aug 27, 2011 at 1:23 AM, Jeff Ward <j...@fuzzybinary.com> wrote:
> > > > Assaf,
> > > > This refers to the ABI, the binary interface, not the API. In previous
> > > > versions of the SDK / Chrome, a compiled .nexe wouldn't even load in a
> > > > mismatched version of Chrome. Here, the nexe is loading and running,
> > but
> > > > the API it's using is unstable.
> > > > Well, it refers to ABI, but this is not the problem. The problem is
> > that
> > > you've used _Dev interface. When you did that you forfeited support:
> > these
> > > interfaces can be broken at any time without any warnings. Once they are
> > > stabilized _Dev prefix is removed and you can use them safely. This is
> > how
> > > Extensions API is changing over time in Chrome, so it's not a new model.
> > > Perhaps this should be noted prominently in release notes...
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Native-Client-Discuss" group.
> > To post to this group, send email to
> > native-client-discuss@googlegroups.com.
> > To unsubscribe from this group, send email to
> > native-client-discuss+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/native-client-discuss?hl=en.
> --
> Christian Stefansen
> Product Manager
> Google
Could you confirm that you are using NACL_PPAPI_ENABLE_DEV=1, pp::Graphics3D_Dev (given that you're using rev 98412), --enable-nacl, and --enable-accelerated-plugins?
If you are, could you send some code we can look at?
On Mon, Aug 29, 2011 at 2:44 PM, pps <prasad.si...@gmail.com> wrote: > Hi,
> I got the latest? SDK (0.5.1052) and tried to create a little GL app > (compiles/links fine), but running it in build 98412 fails because > glInitializePPAPI(..) in the module Init() method is returning false.
> I also tried 97282 and 15.0.865.0 canary and found the same issue. FYI > - the module runs fine, but glInitializePPAPI() is returning false.
> Does anyone else have this problem? Anyone have a list of cases where > the call may fail?
> Thanks! > Prasad
> On Aug 26, 6:31 pm, Christian Stefansen <cstefan...@google.com> wrote: > > Thanks, everybody, for trying out the cutting edge Chrome and for > reporting > > the issues!
> > As others have mentioned, sporadic breakages are likely to occur while > the > > 3D interfaces are in dev/. Chrome auto-updates itself when a newer > version > > is available on the given channel (stable, beta, dev, or canary), and it > is > > not possible to turn this off. To avoid potential breakage when this > > happens, you can use known good versions of Chromium, Chrome's non-Google > > branded sibling, which does not auto-update itself. You can find Chromium > > builds athttp:// > commondatastorage.googleapis.com/chromium-browser-continuous/i... > > .
> > Known good builds of Chromium include revisions 96198 and 97282 (using > > pp::Surface3D_Dev and pp::Context3D_Dev) and revision 98412 (using the > newer > > pp::Graphics3D_Dev). If you are using the currently released SDK, you > should > > use one of the former; if you feel adventurous and don't mind checking > stuff > > out from our repositories, you can use the latter.
> > ABI stability means that a nexe will continue to work from the first > version > > where all the interfaces it uses were out of dev/ and onwards. It does > not > > mean the APIs won't change in newer versions (potentially necessitating > > adjustments when recompiling).
> > We are working on getting the 3D interfaces stabilized, so that we can > pull > > them out of dev/. When that happens you will be able to use Chrome for > > development purposes. Coming interfaces such as full-screen, mouse lock, > > peer-to-peer networking, and Web Sockets will go through the same > process: > > early adopters who are keen to get started may want to use known good > builds > > of Chromium to shield themselves from the churn until the interfaces are > out > > of dev/.
> > Cheers, > > Christian
> > On Fri, Aug 26, 2011 at 2:39 PM, Assaf Raman <assafra...@gmail.com> > wrote: > > > I understand. > > > I disabled all my demo pages and added a note about this issue - until > > > it is resolved. > > > Note that you have links to my OGRE NaCl demo in some of your issues. > > > I will update the demos soon after you will release the next SDK (0.6) > > > - and re-enable the pages. > > > Keep up the good work, as I wrote - moving 3d to be a stable feature > > > is something all of us in the OGRE community wait for. > > > I even have the code for the first NaCl OGRE 3d game that will be in > > > the app store (a GPL 3d chess).
> > > Cheers,
> > > Assaf
> > > On Aug 27, 12:26 am, Victor Khimenko <k...@google.com> wrote: > > > > On Sat, Aug 27, 2011 at 1:23 AM, Jeff Ward <j...@fuzzybinary.com> > wrote: > > > > > Assaf,
> > > > > This refers to the ABI, the binary interface, not the API. In > previous > > > > > versions of the SDK / Chrome, a compiled .nexe wouldn't even load > in a > > > > > mismatched version of Chrome. Here, the nexe is loading and > running, > > > but > > > > > the API it's using is unstable.
> > > > > Well, it refers to ABI, but this is not the problem. The problem is > > > that
> > > > you've used _Dev interface. When you did that you forfeited support: > > > these > > > > interfaces can be broken at any time without any warnings. Once they > are > > > > stabilized _Dev prefix is removed and you can use them safely. This > is > > > how > > > > Extensions API is changing over time in Chrome, so it's not a new > model.
> > > > Perhaps this should be noted prominently in release notes...
> > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Native-Client-Discuss" group. > > > To post to this group, send email to > > > native-client-discuss@googlegroups.com. > > > To unsubscribe from this group, send email to > > > native-client-discuss+unsubscribe@googlegroups.com. > > > For more options, visit this group at > > >http://groups.google.com/group/native-client-discuss?hl=en.
> > -- > > Christian Stefansen > > Product Manager > > Google
> -- > You received this message because you are subscribed to the Google Groups > "Native-Client-Discuss" group. > To post to this group, send email to > native-client-discuss@googlegroups.com. > To unsubscribe from this group, send email to > native-client-discuss+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/native-client-discuss?hl=en.
