Jump to content
The simFlight Network Forums

dolph98

Members
  • Posts

    39
  • Joined

  • Last visited

dolph98's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I forgot to add that I'm doing it in the air, as suggested on other posts I read earlier. I get the same result in the air. I see what you mean about travelling thru the "armed" region. I have no idea how I got around that before. I don't know what I did in the past but I was able to do this in a 0-100% manner before. Now I can't get it to do it no matter what I try. I have done many, many descents with the throttle minimum and nose pointed downward using the spoilers to maintain a 250 knot airspeed. I have viewed them externally and they were adjustable per that axis. I ain't making this up. So I guess I may have to change the way I do things unless I stumble on the answer - in which case I'll share it here. Thanks.
  2. Hi Pete, Customary compliment: I love your software. It is simply the best FS purchase I ever made. Problem statement: I cannot make the spoilers activate/deactivate with a linear travel in between with an assigned controller axis. Versions: I'm using FSUIPC v4.909 with FSX/Acceleration on a CH system consisting of CH Fighterstick, Pro Throttle, and Pedals (all USB) programmed with CH Control Manager v4.55. To be clear, when I use the CH software to program the buttons and such, I make sure all axes are unknown or unprogrammed in that software (all axes are set to DX mode) so that I may use FSUIPC exclusively for all calibrations/axis assignments (no axes assigned in FSX Options/Settings/Controls menu). Note that the CH software calibration function shows a linear 0 to max travel on the Fighterstick's Z-axis, with no center position or detent. However, FSUIPC sees that axis with a center detent or zero position in the middle. I had everything working correctly in the past until I reverted to v4.7 as a fellow simmer suggested as a fix to cure another problem (which did not help). Now that I'm back to v4.9 I cannot get the spoiler axis to act correctly no matter what I try. I cannot remember exactly what I did in the past to make this axis work correctly. The only difference I can see is that I'm using your latest v4.909 rather than v4.900 as in the past. To answer an obvious question before it's asked: yes, I tried that version too with the same results. And I had the same problem this time around with v4.7, which is the main reason I went back to the v4.9 version in the first place. I deleted the .ini to allow a fresh start and all other axes act correctly except the Z-axis on the Fighterstick, which is meant to be used as throttle control if used standalone, but I wish to use it as spoiler control. So when I get into FSUIPC, that axis shows a detent and I cannot make it work the spoilers in a linear fashion. Instead, it intermittently fully activates the spoilers and I cannot deactivate them, or it does nothing at all. Not sure what is happening. I have tried a couple of different jets that have spoilers and all act the same. I suspect that if I could make FSUIPC see that axis as a linear potentiometer, instead of having a center detent, everything would be fine. Is there a way to make it so? Thanks in advance.
  3. Ok, thanks guys. Pete, I will do as you suggest and try making it RO for now. Maybe the culprit will fail and propogate an error to some level I can see what is doing it.
  4. Hi, I am using FSUIPC 4.853 and am flying using the VRS TacPack open beta. These are the only two entries I have in my dll.xml file: <Launch.Addon> <Name>VRS_TacPack</Name> <Disabled>False</Disabled> <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> Upon closing FSX I get a stack_hash error if FSUIPC is loaded first. This does not interfere with my flight sim enjoyment but I just don't want the error. So I found that by putting the TacPack entry first, the error goes away. But after flight, FSUIPC is again first in the list and I get the stack_hash again. Question: Is there some reason FSUIPC needs to be first to load and is it changing the file automatically? If not, any idea what is changing it? Is FSX doing it? (okay, that's three questions...) BTW, VRS has it on their list of things to fix eventually, it appears that Tac_Pack does not quite clean up after itself and causes this stack-hash on some PCs. It's not a bug per se, but it bugs me. Thanks in advance.
  5. Thanks for the tip. I will have a look at FSUIPC SDK.
  6. And the verdict is in. You, Pete, are a hero. Using your suggestion for location pokes, my system works just fine running SpeechBuddy and RC4 on the laptop client and controlling the main FSX machine! So now alls I have to do is come up with a good script and I'm in business, and you saved me $60CD! The only other thing I would like IYP for is the checklist feature and SpeechBuddy does that too so I am satisfied. Thanks again! Dolph
  7. My pleasure. Here's the link: http://www.itsyourplane.eu/forums/viewtopic.php?f=3&t=424 Looks like it was posted way way back - yesterday. Yes, 65586 is left over from the old function I used as a model since I control the magnetos myself from the panel. Since I don't know DWS language (apparently SpeechBuddy's custom native language) and cannot find a syntax guide, I had to "borrow" another function to add RC4 calls - in this case I borrowed the magneto control function. It is used merely to assign a value into the newly declared variable 'ATCValue'. Assigning a variable may or may not be required in DWS language. It gets replaced with whichever key value once the function is called from the XML. I could have used any number, but changed it to 817 now to avoid further confusion. Why are locations 3110 and 3114 not mentioned in any manual I got with FSUIPC? I will try your method and let you know. Thanks Pete!
  8. Pete, Here's the SpeechBuddy handler for atc calls: // ATC Handler procedure ATC( sentence : string ); begin var ATCValue : integer = 65586; if SpeechDisabled then exit; case VarValue( 'ATC' ) of '1' : ATCValue := 817; //ctl + shf + 1 = 817 '2' : ATCValue := 818; '3' : ATCValue := 819; '4' : ATCValue := 820; '5' : ATCValue := 821; '/' : ATCValue := 959; '7' : ATCValue := 823; '6' : ATCValue := 822; end; speak(sentence); FSUIPC_SetInt( $3110, ATCValue ); //should this be 1070? end; The question is should I be using $3110 for these commands? If so, it doesn't work. I then tried sending them to $1070 and still nothing. I am practicing on the FSX PC and will move the script to the laptop later once it works. I have reset the RC4 keys to default. I also read in the Its Your Plane support forum that the Radar Contact program must be installed on the FSX machine, which is contrary to what I am trying to achieve - unloading the FSX machine to run only FSX. The developer, one Robert Cezar, told a user in no uncertain terms: "REGARDING: It's too bad , I would like to have radar contact and IYP working together on the client system keeping the fsx system cpu only for fsx. You are correct. RC needs to be on the Simulator PC. I fail to see why this is so arduous." This whole voice thing is not going to work for me if that is the case. The audio will then be coming through the FSX PC speakers and I will be wearing a headset for nothing. As it stands, only the FSX audio comes out the PC speakers, and the RC4 voice comes through the headset connected to the laptop. I guess I want too much, eh? I am losing enthusiasm after I read that. Actually, I got the program "Shoot" to work quite well for the time being, but I have to run it along with RC4 on the FSX PC. I really want to figure this out so everything is offloaded to the laptop. Cheers!
  9. Yes, I agree that it has to be the codes and not keypresses that are needed. So I need to figure out what codes to send. I have already cleared certain functions in FSX setup like the ADF, COM, and some others I never use so they are free keys for SpeechBuddy. Since they are common, I should be able to pick them out of the sample files I have already along with your .pdf listing. Will play with it.
  10. "That should be all I need" is right, keyword being should. I've been on time compression here but I had a chance to revert to the original SpeechBuddy .xml that worked yesterday. I can get it to work if I use "!", "@", etc. but those conflict with the shift 1,2,3 etc. that we all use to pop up a window on the 2D panel. So I have some reorganizing to do in the FSX controls setup. I tried remapping simple keys like t, c, x, that I don't use but they don't work for some reason. I am mystified why some keys work and some don't. Any key should work if it is unmapped in FSX and mapped in the SB .xml file. The other mystery is why it works on the FSX machine but not on the laptop. As I said, the FS2004 .xml does indeed work from the laptop to control the FSX functions so why not this .xml? I'll get there, persistence being my middle name. Again, this is an experiment and learning something should be imminent. I will share with you here what I find so others can use the info.
  11. I did download the new version .dll. Thanks. Well, after I wrote that last comment about being very happy, I'm very sad. Seems I misled myself and it only worked that one time, I can't get a repeat performance no matter what I try. Also, that one time was with it running on the FSX machine, so when I tried it on the laptop and it failed to control RC4, I tried again on the FSX machine and it would not work. I have no idea how or why it worked in the first place. I may wait until I have $60CD and get IYP but that could be months. Wife has other ideas for the money. Flight Sim Experience Improvement comes after Home Improvement ya know.
  12. Hey Pete! I finally got it! It was right under my nose the whole time. SpeechBuddy does not seem to send the "+^1" (CTL SHF 1) properly. But it does send "+1" (SHF 1) if I program it as "!" or two would be "@". I'm very happy now. BTW it will also do checklist reading for me so that's my next step in my programming adventure after I work out all of Radar Contact's possible responses. Thanks for your help in this. And thanks very much for FSUIPC - that was probably the best purchase I ever made. It helps with my weather issues with ASE and now it will help with my voice activation. You probably don't get thanked enough for that magical piece of software. Dolph
  13. Well I went ahead and experimented using SpeechBuddy on my FSX machine. Again, it controls all FSX functions but does not work with RC4 at all. I reprogrammed the keys as you suggested to Ctl SH 1 etc. with no joy. I made up a quick fake interface just to play with the flaps and was able to move the flaps up and down with any command I speak, but I cannot get it to control the RC4 input buttons no matter how I program them in FSX or RC4. Something tells me I'm close but I can't quite put my finger on it. I don't get what is different about the RC4 menu - it gets it's input through FSUIPC so it should be working. Thanks for your replies. I may give up until I can shell out for IYP.
  14. Thanks Pete. Yes, the file is dated Dec. 2006. It's available at AVSIM but it takes some doing to make it work under Windows 7. It has been a pleasure reaping the benefits of FSUIPC over the years, and this latest add-on, voice activated ATC for cheap, will not beat me down.
  15. SpeechBuddy's not working for me. RC4 works fine over WideFS but the commands to control it do not. I have looked at IYP and that program is not exactly what I want right now. Plus I don't have $60CD to part with. I need to fly for awhile and look at this some more over the weekend. Too bad I am a day late and a dollar short getting that free SuperATC package. I remember seeing something about it some time ago but I wasn't interested in voice activation at the time.
×
×
  • 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.