jwk737

Members
  • Content Count

    41
  • Joined

  • Last visited

Community Reputation

1 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No
  1. jwk737

    Viewing instruments on remote computer

    Hi, fsxspy has it's own forum now, maybe that is a better place. But if fsxspy doesn't work for you, you can always use the flight1's 30 days refund policy. hth Johan
  2. jwk737

    Viewing instruments on remote computer

    Yes, it is available for a while already. Please visit www.fsxspy.com for more info, order info and downloads. Currently the forum is floaded with fake registrations, so please send me a pm also, so i can manually approve it. Cheers, Johan
  3. jwk737

    Viewing instruments on remote computer

    Yes, it is pretty much optimized and stable now. I will do some last testing with the web dcu version and update the manual. Two more weeks maybe. You can pm me if you want an early notice. Cheers, Johan
  4. jwk737

    Viewing instruments on remote computer

    > Then I remembered I use DX10, so swapped back to DX9 and it worked fine. > Any chance of DX10 compatability? Thanks for filling me in on that. It's very specific for DX9 right now but DX10 shouldn't be a problem either, I will look into it when I finished the manual. > Could you confirm that this is correct, and clarify whether this feature will be available on the multi-channel payware version. Input source cropping will be implemented in the payware version like it was in 0.5 albeit slightly different but more flexible, Regards, Johan
  5. jwk737

    Viewing instruments on remote computer

    Hi Lucs, port #8737 is used for the webserver, port #8738 is used for internal communication between the console, fsx and the viewers. The full url should indeed be http://<fsxmachine>:8737 where <fsxmachine> is either your fsx computer name or it's ip address (so e.g. http://pc-johan:8737 or http://192.168.1.14:8737) Other people commented as well on the lack of a decent manual, it is top priority right now and I hope to finish it in the next few days. The free version is a complete functional remote/web DCU, which coincides with a limited (mostly being single channel) evaluation version of the multi channel FSXSpy Pro package. I think 5 fps is enough for a DCU; you probably can't type any faster and the screen won't be updated with new info 5 times per second either. But I agree, it's sub-optimal. The pro version obviously doesn't has this limitation, but even then I think 5 fps is enough for a DCU. The PFD, ND and Eicas might need more, but there is no such thing as a free ride and since the cpu is the most limiting factor in fsx, one has to compromise between fps on the outside views and on the remote instruments. Then the 50% fps drop which is unexpected and unacceptable. It has been extentively tested on i5/2.2Ghz and i7/3.4-4.7Ghz with resp. a GTX560 and a HD6870 where an average frame drop has been noted of 5 to 8% with 8 (!) instruments from the NGX. Your milage will vary but I would like to hear if more people are suffering from frame loss more than 10% and with what configuration Thanks and Regards, Johan
  6. jwk737

    Viewing instruments on remote computer

    Hello Lucas, Could you add a little bit of info on this please? Console: - Do the panels (recorders) show up in the recorders pane, assuming you do have undocked panels? - When you select a recorder, does it show up in the preview pane, check "Live"? - Does your fps drop already at this stage? Please you do a ctrl-C (copy) in the log pane and ctrl-V (paste) it in a pm so I have a look at it. NB: the "always on top" option in the console also makes the console transparent, which is very usefull for alligning and experimenting but is a real fps killer (everything has to drawn twice). Please switch is off Web client: - What do you see when pointing your browser to localhost:8737 from the fsx machine? - What do you see when pointing your browser to <fsxmachine>:8737 from another machine (fsxmachine is either the name or an ipaddress) Viewers: On vhhx, in the NGX, fps drops from 34 to 31 on my machine, which is to be expected. Just the existence of extra panels takes extra time to compose, even though they maybe hidden and thus not presented. Thanks and Regards, Johan
  7. jwk737

    Viewing instruments on remote computer

    Yes sure. It's based on the same beta that is out now for the free version.So both versions will benefit from each other in that regard. I hope to find a suitable forum too though, were people can help each other much quicker and often from a more practical view then the author. Johan
  8. jwk737

    Viewing instruments on remote computer

    Hi, thanks. Some interesting suggestions, I'll keep them in mind. The viewers do, no need for the server I guess. You do have to explicitly save the viewers layout with the button in the channel guide, maybe that is it? Configurable. An image like e.g. a cdu requires and other encoding that e.g. a graphical pfd. Positioning is simply dragging with the mouse. Resize is mousewheel with shift and/or control et al. But I see your point. Maybe we need an advanced config editor or the like. Relating capturing, that has completely changed in v1.0.3. It hooks itself inside the directx render engine and tees the surfaces on request even before being rendered on the screen. The v0.5 way was experimental, not optimized gdi and is now obsolete. Please hangon until 1.0.3, you'l be surprised . Gr, Johan
  9. jwk737

    Viewing instruments on remote computer

    That is definitely going to impact your frame rate. I think you´d better hold your breath until the 1.0.3 release. Then you can hide the panels regaining fps almost as not displaying them at all. I am experimenting with rle and other more graphically suitable encoders. Right now 0.5 is just jpeg and 1.0.3 is motion jpg. Doesn´t flipping the `bounds´ checkbox takes care of that? Sure, only complete windows (that's why they must be undocked) are captioned. The selection in the server sets the parts that will be transmitted. HTH Johan
  10. jwk737

    Viewing instruments on remote computer

    As it happened, last weekend I updated the front page of FSXSpy website to reflect the latest 1.0.3 release that is currently in beta. I must have deleted the download links while doing so, fortunately I could recover them with a few mouse clicks. The 1.0.3 release will be available very shortly and contains: - highly improved capture engine, using direct3d instead of gdi allowing - panels can stay invisibile after setup - mouse clicks send back to fsx - http (web) server build-in. Yes, that's a complete web DCU. The single channel version will still be freeware, the multichannel cockpit edition will probably become available as payware and contains much more features and goodies. The latter being specially suited for home cockpit builders. Right now you can only download the 0.5 version, 1.0.3 is in beta but should not take more that 1 or 2 weeks from now. Read all about it at https://sites.google.com/site/jwk737/home/fsx-spy Cheers, Johan
  11. jwk737

    SDK support

    That is using the dotnet frame work, like visual studio does
  12. jwk737

    SDK support

    You could take a look at https://sites.google...me/pmdg-connect It contains a few complete vs2010 projects including the pmdg example. If you just want to wire your cockpit to the pmdg you should consider a 100% managed approach, it will make live a lot easier and maintainable. Right now I only have sioc with a script with just the var definitions for the io which in C# I read, manipulate and send directly to the pmdg, all interrupt based, no line of c++ or extra sioc-script required. I could refactor this part and submit a new project if you (or someone else) are interested. HTH Johan
  13. jwk737

    Viewing instruments on remote computer

    Sorry it took so long, thought I had an email trigger on this topic? Gerard contacted me by email, i think i should repeat my reply here. Your outside view screens are high res (and so are pretty cheap beamers nowadays) and your mip panels probably aren't, so the 400x400 pixels will be larger anyways. The transmitted pixels are 1:1so it's better to set the size of the instruments to their native or half size, you can find these in panel configs, bitmaps or whatever. This avoids aliasing, and a zoom of 2 will be anti aliased, so I doubt that you will notice the difference. HTH Johan
  14. jwk737

    Viewing instruments on remote computer

    Not yet. If you have a mip (main instruments panel, say the cockpits "dashboard") and you have a monitor (or 2,3 or 4) to display instruments in the mip, you can use the wasted screen space covered by the mip as a "parking area" so the panels are out of site. The extra 4 monitors do however have an impact on your fps of the outside view on another monitor set of 3,5,.. So it is better to have just one extra screen where you park all the panels or perhaps create one panel with all the wanted gauges, haven't tried that. Now fsx only has to render the reasonably scaled panels on one extra screen, fsx spy distributes from there. HTH, Johan
  15. jwk737

    Viewing instruments on remote computer

    Hi All, It took a while but version 0.5 is ready. The main new feature is the "FSX Spy - Channel Guide", a sort of control center to select channels for viewing, and an overview and status of the seperate viewers. This Guide also takes care of viewers persistency. The seconds main new feature is the server now having the possibility to pixel precise (or automatically on startup) resize and position the panels, auto undock (maybe hide?) will be for a next release. Some smaller items: - server: better handling of restarts, border/inside move/zoom for fine tuning selection - viewer: rotate/flip You can find it here: https://sites.google...37/home/fsx-spy please uninstall any previous version first. Have fun!