August 26, 200916 yr I am fairly proficient with VB6/VBA, but this is my first serious need for .Net, so could use a little guidance. I understand the bias towards C# here, but would like to stay with VB if possible.I would like to override the simulation and feed FSX with my own parameters. Ultimately I would be feeding LAT/LON/Altitude/Attitude/Airspeed/Control surface position, etc.Can anyone thow together a quick VB app that shows me how to do this?If anyone wants to call dibs and help me out with this off-line, I would be happy to PayPal you $50, or if we solve it here on the forum, I will drop that in the AVSIM donation box.I am running FSX SP2, FSX SDK SP2, and VB 2008 Express.Thanks in advance,-Sky
August 28, 200916 yr Hi Sky.If you wish to stay with VB6, look at this:http://www.fsdeveloper.com/wiki/index.php?...cessing_from_VBIf you wish a VB.Net example, the FSX SDK does have an example named "Managed VB Data Request"Dick
August 30, 200916 yr Yup.. settıng the data ıs just the exact opposıte, so it's really like one line that needs to be changed. And for reference I recommend the ESP sdk documentation not the FSX ones, but use the FSX SDK for compiling. Also you need to turn the FREEZE_LAT and FREEZE lon and alt off. or ıs ıt on... anyways there are a few other varıables you need as well. I would recommend readıng the FS2004 Netpıpes/Flight Data Recorder SDK to get an ıdea of what those are... enjoy the debuggıng!!! that should get you poınted ın the rıght dırectıon, your skılls wıll need to carry you the rest of the way...and the prefered language ıs C not C#:) C# is just as evil as VB since they pretty much result in the same .NET/CLR bytecode.
August 31, 200916 yr Nothing wrong with .Net/CLR (it JITs down to native code before running). You can try my new replacement Managed SimConnect SDK (see link to blog in sig below). I haven't included any VB.Net samples in there yet, as I don't do VB normally (C# works fine for me :-> ), but do plan to port 1 or 2 of the samples to VB before final release. My SDK has several advantages over the original, at least for managed code developers, including: No reliance on anything installed by the SimConnect.MSI file (neither the Global Assembly Cache version of the Microsoft.FlightSimulator.SimConnect.DLL or the WinSxS version of the native SimConnect.DLL), you ship/install my BeatlesBlog.SimConnect.DLL with your app (or you can even "link" it into your app using ILMerge or a similar tool) Written in 100% managed code Understands .Net types better Uses custom attributes to define/register the data structures you use with RequestData/SetData calls Client Data Areas actually work (these are broken in the original SDK managed wrapper) Supports running in limited trust environments Library included for building Silverlight based clients also (see http://BeatlesBlog.cloudapp.net for info/samples) One caveat, my library only supports FSX SP2 or later (ie FSX SP2, Acceleration, or ESP v1).Timhttp://beatlesblog.spaces.live.com Tim http://fsandm.wordpress.com
Create an account or sign in to comment