I'm trying to get VideoTexture working in an Adobe Air app and I'm having real trouble with the basics and getting it working on my machine.
I'm also using Stage3Dproxy and I wonder if this causes the problem, but Context3D.supportsVideoTexture is always undefined.
I've got a fairly hefty NVIDIA GeForce GTX 850M which I think is fairly new and should be upto the job!?
The Adobe Stage3D support swf never loads for me, so I'm wondering if this relates to the problem
https://helpx.adobe.com/x-productkb/multi/stage3d-unsupported-chipsets-drivers-flash.html
Anyone else had this issue?
#BotMaster was right - I'd not set the right swf-version in this particular project file.
Related
I am facing issues to run .exe files created in Qt 5.3 on different windows system. I have included all the .dll files. The issue is that on the latest system with graphics card support the application runs without any issues but on older systems it just gives blanck screen.
I suspect that this has something to do with openGL support for the system.
Is there a way where I can make sure that the application runs without any glitches on all the systems?
Or is it possible to have an application created without oprnGL support needed ?
Hoping to hear some solution for this.
Thanks in advance.
EDIT:
Following is the error I get when I run the code
getProcAddress: Unable to resolve 'glBindFramebuffer'
getProcAddress: Unable to resolve 'glBindFramebufferOES'
getProcAddress: Unable to resolve 'glBindFramebufferARB'
and here is the screenshot of the way the screen looks
NOTE :
Please note that when I run the .exe on a new system with updated graphics, the screens looks perfect.
Did you include any OpenGL headers in your Qt Project?
Because if you did then there is obviously going to be a dependency on OpenGL for each system and if one of them cannot support this then you either need to decrease the minimum version of GL you are using or remove these headers altogether. It is also worth noting that no matter how hard you try - you will never get the same version of OpenGL to run across every piece of hardware without having to change something.
Did you add the QtOpenGL module?
From what is sounds like, you are not using OpenGL in your application. If this is true then you should remove this module from your .pro file and it should remove the dependency.
I hope this answers your question. If not, could you provide a little more detail because your question was slightly vague.
I've recently purchased some beginner books on basic ActionScript animation and also downloaded the flashDevelop IDE. I've taken a couple Java classes and have a VERY basic understanding of coding and at that, computers in general. I'm having a difficult time figuring out this IDE (eclipse was setup for me). I've downloaded the file and installed the IDE. I made a file and wrote some code but when trying to compile I get some sort of pathway error and also an SDK error. I'm completely lost on how to fix these issues as the results I've found through Google and stackoverflow are not simplified enough. I'm also confused about how this ActionScript code will be turned into, say, a ball jumping around the screen. Could I please get a VERY simple, borderline special needs explanation of how to setup this IDE and also any info on additional programs needed to actually turn the code into an animation? Forgive me for my ignorance, but I'm starting from the ground up and any help will be much appreciated. Thank you
You may try Flash Builder, and you could change different version of sdk in flash builder. http://www.adobe.com/cn/products/flash-builder.html
has anyone been able to use Workers in AIR Application built with Flex 4.9.1 and AIR 3.7?
I wanted to give it a try for a project, but as soon as I include/setup the worker like in the tutorial made by Lee Brimelow, my Application "freezes". Which means: It does not start. The compiler compiles, I get the info-text in the console, but neither my window opens nor my does any of my events get fired.
Ideas anyone :) ?
Quite simple solution. Simply add
-swf-version=XX //XX must be >=17
as a compiler argument and it works. I think this is a bit weird, since I am using AIR 3.7 but okay, whatever it takes :)
ANSWER To use this and any new features in 11.2, the swf-version needs to be turned all the way up to 15.
My setup:
FlashBuilder 4.6 Build instructions include "-swf-version=13"
Flex SDK version 4.6.0 (build 23201) playerglobal.swc (current one from
Adobe's page,
http://www.adobe.com/support/flashplayer/downloads.html, said to be
11.2 as well)
Standalone debugger projector (11.2.202.228)
Browser flash player plugin (11.2.202.228)
So by my reckoning, I'm up to date in everywhere I should be, to be able to use MouseEvent.RIGHT_CLICK (Adobe Documentation:
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/events/MouseEvent.html#RIGHT_CLICK) but, if I do
I understand that right-click was initially supposed to be AIR only, but that's supposedly changed, which is supported by the fact that it's in the website documentation and in the class definition for MouseEvent,
I want to play around with a few right-click stuff in Flash, but it seems like something's definitely not working correctly. Anyone got an insight as to what's wrong?
I'm a bit confused by some of the comments, so in case it's me poorly explaining what's going on, so here's an example of my code running and compiled, with source attached,
http://www.tymonrovers.com/seaders/asdf.html
SWF Version in build instructions need to be up at 15... as detailed http://helpx.adobe.com/flash-player/release-note/release-notes-developer-flash-player.html#main_authoring_flash_player
Damnit! I know it looks obvious now, but I do think they should probably detail that in the docs as well, they've got the specific versions of the SDKS for AIR and Flash, but not the swf version info, which while it might sound overkill, would certainly solve irritations like this when you forget that one little bit of a tweak you need to do for new features. Ah well, all working now. :/
-swf-version=15
I've just stumbled upon a case when Flash app freezes in production Flash Player and works smoothly in a debug version. It doesn't throw any errors or exceptions. Has anyone ever encountered anything like this? Why is it happening or how one is supposed to debug in such case?
And a side question - what exactly is different in debug version from internal point of view? Any good writeup on the topic?
UPDATE:
I didn't mention, but the trouble is with Flash Player 11, it probably matters, cause Flash Player 10 doesn't have any problems with the same code.
In case anyone wonders here how this problem got solved.
First of all the class that was causing the hang turned out to be nifty BitmapDataUnlimited, which makes possible to overcome bitmap resolution constrain in Flash. Basically what we've changed was that we made a class directly extending EventDispatcher, rather then implementing IEventDispatcher interface and having indirect deal with private internal _eventDispatcher object.
Can anyone tell me what's the benefit of implementing IEventDispatcher interface directly?