Was installing FD4.0 including all defaults on Win7 64bit with Java on. FD was starting but debug didn't work. Checked all google entries for some notes, uninstall an installing several times. To avoid time consuming Flex and AIR donwloads I copied tools/flexsdk to c:/lib/flexsdk. Therefore I did the entries in 'Programm Setting' manual. FD is running but in DEBUG mode it doesn't debug and returns [No debug Flash player connection request]. What to do now?
many thx.

Have you told FD there your debug player is? And configured to use it?

Go to settings -> FlashViewer -> External player path.

then in project Parameters -> Output -> Test project : Play:External player.

I am also having a similar problem. I got the most recent version of the Flash Debug Player (all of them in fact, sa, plugin, activex). I also have the most recent version of Flex MPL.

All I want is to get my test movie button to build/launch the swf in the debug player and feed debug output like trace statements etc to the Output panel. The Logs panel would be fine as well but is not preferred.

However, the test movie button only launches a blank player with no swf loaded and the only way I can get my swf to actually load up immediately (without having to use the File menu in Flash Debug Player to open it manually) is to set my Project Properties to Open Document "$(OutputDir)\$(OutputName)".

And again, I have no debug output. At this point it's like I may as well be writing PHP in notepad.



Thanks

@ Deril

yes, I did the entries in 'Programm Setting' and in Project. I even tried several different combinations for flexSDK and the FlashDebugger.exe

I forgot to say. I was even using 32bit for viewing and 64bit for debugging. With this try I made sure that FD was calling the correct Flash exe. It does. But the focus doesn't return to the breakpoint of FD.

Got no clue why, but it is running now!!

To help others at least as good as I can, here what I did so far, or what I recommend to do.

As other posts already noticed, check your installation, that is Java, Flex, AIR installed. If you need to reinstall FD move tools/flexsdk outside of FD installation dir and remove checkboxes for flex/AIR download at installation.

When FD is running - now it comes: go to Tools/Programm Settings and set AS3Context to your moved flexsdk. And FlashViewer to the location of the debugger like C:\_libraries\flexsdk\FlashPlayerDebugger.exe. If you run 64bit play arround with 32bit and 64bit - on my 64bit win7 system it is running with 32bit debugger Vers. 10.

Also check menu Project/Properties. Play arround 'output platform' and 'play project'. FD is now on FlashPlayer 11.2 and Other IDE and 'Play: Default'.

I am under the impression that once you setup a invalid combination FD is not refreshing the new setup properly. This is why I got no idea how FD was switching back to Test Project - 'Play: Default'. I didn't do it myself.

But omg won't touch it again (for the next days) - I need to make some money and get some code out of FD by now. Unfortunately I can't provide any bug report to follow. The final success was not understood. Also I don't understand the logic between three different versions of Flash Players making sence in my setup. The published Player in Adobe Setup ist 9.0 - FD is requesting 11.2 and the debugger runs on 10.0. Will I understand this once? But it is running now. brrrrr

I had the same problem.

The problem was possibly, and still is, that Project Properties under "Test" don't show the "Play ..." options.

To fix this problem, I wanted to isolate if it was Haxe or FD in general. So I created a new AS3 project, and was successfully able to debug (Project Properties > Platform = Flash).

I then tried the same setting (Project Properties > Platform > Flash) in NME. It didn't work, and it butchered my NMML file. So I reverted my changes (say Mercurial), tried debugging the project again, and it worked!

Definitely a "what the ...?!" moment.