Jump to content
The simFlight Network Forums

jordanmoore

Members
  • Posts

    10
  • Joined

  • Last visited

About jordanmoore

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://www.hovercontrol.com

Profile Information

  • Location
    Syracuse, NY
  • Interests
    Helicopters

jordanmoore's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Pete, It was in fact my mishandling of the byte length (2 vs. 4). Thank you for helping me.
  2. Thanks Pete, I appreciate your patience. I was certain that something so widely used would put the problem in my court for sure. The information and advice you have given will certainly get me sorted out. I'll get to working through that right now. I'm thinking that your 2/4 byte question is the first thing I'm going to check. I apologize for not using the logs more effectively before contacting you. I don't know my way around the logging capability that well as of yet, and part of that is due to the fact that FSUIPC just works so well (and as described) that I rarely have problems that require log examinations! Thanks again, and all the best to you.
  3. Hi Pete, Haven't written you in a while. Hope this finds you well. Do you remember that I said I was working on a fun project and had decided to use FSUIPC instead of simconnect because I desired the possibility of cross-platform capability? Well, I am just getting to the point where I am beta testing my project with a few friends, and I only cared about getting it to work properly in FS9 at first, but one of my guys went ahead and tried it against FSX, and damn if it didn't basically work on the first try. I did nothing to make sure that this would be the case...so I'm pretty impressed. That is really exciting. I have one data issue that I can't make sense of. The on ground flag 0366 that I'm reading in my program works properly when the client is connected against FS9 via FSUIPC. However, we noticed on the FSX connection (via FSUIPC) that the on ground flag seems to be set to true at all times. All of the other data calls appear to be working as expected and producing the outcome I would expect, so I figured maybe something changed aroud this one particular item, or perhaps you could give me more insight as to how I might have implemented it incorrectly. Has anyone else mentioned anything wierd around the on ground flag? Thanks for the help, and I'll just say again how much I appreciate what you do.
  4. Thanks again Pete, Your responses have been very helpful. Even if FSX had a 75% adoption right now, I would still want to reach the other 25% if I could. (I think the adoption of FSX as primary sim among Hovercontrol's audience is sub 10%, and that is a generous guess) So I see myself becoming very friendly with FSUIPC for some time to come. Not to mention the fact that now that I have my "mojo" for working with it, I'm finding it to be a very productive interface. I just wish I had started working with FSUIPC more seriously earlier on. I spent most of my development effort on aircraft. I'm only just now really starting to get into it heavily and having a lot of fun. I did one small FSUIPC client app several years ago, but it was very minimal in its functionality (it manipulated fuel levels to simulate load weight on helicopters). That's why I said I was "behind the times". Gotta catch up now. Any way, thanks again. I guess I'll get back to work now. I'll see you when I have my next big question that is clearly included in the documentation LOL. (actually I have been a heavy user of your programming guide, just not so much with the user guide).
  5. Thanks Pete, Good points. I had a hard time reading the red over green, but like you said, a friend of mine thought the red over green was just fine. The case for programatic control of the text color might be that someone builds a cool free widget using FSUIPC and wants to give the user a choice of the text color, because the user probably doesn't have that choice through unregistered FSUIPC (correct me if I'm wrong). But that brings up a good question as to whether the text color is a nice-to-have and should only be available in registered FSUIPC clients, or is it a need-to-have, in which case programatic control would be nice for a developer. So that he/she could extend it to his users through is own application. I was just happy that I could change the color through the client tabs. But if you ever add programatic control of it through FSUIPC, I will certainly take advantage of it. I can't speak for other developers on the subject. By the way, I always enjoy reading your FSX feedbacks in the newsgroups. I think you bring up a lot of important points, that not too many people would notice/raise without the deep understanding of the sim. If it weren't for you, I think some very important topics would be overlooked. We will all benefit from your feedback, in time. QUESTION: I am working on a neat little client that will do some fun stuff in Flight Simulator (I know, pretty vague). I am currently working in FS9. I am using the FSUIPC interface to get mostly basic information about the aircraft (alt, airspeed, heading, location, yada, yada). I don't believe I am using any advanced functions of the interface (weather, etc). Ultimately, I want to build a client that would work in both FS9/FSX. But because I have not used FSUIPC for FSX yet, I have no idea if this cross-version capability is just a pipe-dream. But as a programmer, I have to guess that this is the whole reason that you are creating new FSX versions of FSUIPC. Growing pains aside, do you think this is a realistic goal for me to have? Provided that I am only using the FSUIPC interface for retrieving mostly basic user-aircraft (not AI) information? I know you probably get asked questions of that nature a lot right now, so I'm not expecting a long answer (unless you feel like giving one of course, I'll take what I can get!). One of the reasons I chose FSUIPC for this idea of mine was because I didn't want to limit my idea to only SimConnect in FSX.
  6. Hi Pete, Haven't spoken in a while, I hope this finds you well. I have really been enjoying working with FSUIPC for FS9 lately. I know, I'm totally behind the times, but I feel like I'm just starting to develop a full appreciation for it. Is there any way to programatically control the white-text user option? Or is this an option that MUST be set by the user via their FSUIPC user options (miscellaneous) tab? I couldn't find a reference to it in the programmer's guide, so I'm assuming it must be set by the user manually, but just in cased I missed something I thought I would ask to be sure. Much appreciated. Thanks in advance!
  7. Of course it will take a little testing and playing to get it fine tuned to perfection, but the initial results show that it is working as designed. Right off the bat it started to produce the effects I have been looking for. I'm sure with some tweaking, I can really perfect the "feel". Pete, thank you, for taking this seriously. It means a lot to those of us working on the 206 in its various forms.
  8. Thank you, you are a gentleman and a scholar! Of course I'm stuck at work, and can only druel over this change until I get home to work on implementing it. Looking forward to it.
  9. Overcontrolling is exactly what the desired result would be. I know you and I are not in the same circles, but I am a fairly experienced helicopter flight sim developer. For example, I recently released a full twin turbine Bell 412, that utilizes a proper startup/shutdown for both engines using the real-world Bell checklist. You could say I'm obsessed. :o) I have the know-how to manipulate "responsiveness" as I need it. But what makes the Bell 206 unique, is that it is responsive on the controls, but that response comes on a delay. This isn't true for all helicopters, but the 206 is unique in this regard (a few others as well). It is what makes it such an interesting and challenging helicopter to learn to fly competently. If you can imagine, you have to make control inputs, and actually wait about 1/4-1/2 second for them to occur. This becomes entirely natural after it is practiced, but it is a very unique aspect that we are most keen to emulate. All of the other shaping, in terms of responsiveness, and curves, we are already able to achieve. A mix of FS control settings, proper airfile configuration, and proper configuration of what limited parameters are available in the .cfg file for the Bell model in FS. As well as some of the extra capabilities that come with the software of various hardware (X52, X45, CH, etc). Unfortunately....none of these options gives us the ability to delay the response. Only make it stronger, weaker, or adjust the curve. This is true for fixed wing airfile development as well. Although I don't do much fixed-wing development, I would imagine this feature might come in handy for a few folks on that side of the fence. If they happen to be obsessed with a particular aircraft that shares this unique control behavior. As far as ini vs. interface. If you were willing to give some attention to my strange request, I would be happy with wherever you put the number. You could hide it in an EXCEL VBscript macro on my P: drive, in an encrypted, password protected gzip file..... if it meant I'd be able to finally crack this nut! lol
  10. Greetings Pete, Longtime user of FSUIPC. Have also done a few freeware programs that used it for various helicopter load-carrying options. In my never ending quest to increase the control response realism for helicopter flight models, I have identified a need that I'm starting to think that only FSUIPC might be able to help me with. Between FS, Saitek software, and FSUIPC, I have been able to control to a good extent the response time and response curves for a particular helicopter. However, there is one aspect of control input that it would seem that I can not get control over. That is delay. I would like to delay the control inputs on a given axis by X miliseconds. Currently, all we have at our disposal appears to be null zone type behavior. Which is unfortunately, not what I need. I would like to be able to move the stick a couple of milimeters to the right or left, and actually have to wait a given number of milliseconds before that control response gets passed to the sim. A parameter to control how long that delay would be, would be most powerful for use in helicopters. Although, I would think any aircraft that has a control system with delay behaviors could benefit from a feature such as this. I know nothing is easy. However, I thought that maybe if I could explain myself well to you, and also describe why I think this would be a valuable feature to many of your users and cockpit builders that you might consider working it into the mix. This is my first time posting in your forum, so I apologize if this topic has been covered in the past, or if I have missed some way to easily do this that already exists. In any case, I thank you for all of the great things we have been able to do via FSUIPC in the helicopter community. It has been a wonderful swiss-army knife!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.