reading1871
-
Posts
43 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by reading1871
-
-
FSXGenius is now in prison in the UK for defrauding simmers who bought PC systems from him.
-
You need Flight1 Soundstream to keep FSX sounds playing when you switch windows
-
I have concerns that not all of the FSX commands are avalable in FSUIPC although I can't for the life of me bring one to mind at the moment.
Fsuipc allows access to many more controls than are available through the FSX controls dialog , please read "FSX\Modules\FSUIPC Documents\List of FSX and P3D controls.pdf" to gain an appreciation of the controls you will have access to through Fsuipc
-
Just tried that method, works well for me, thanks.
Why could Feelthere not have done this, the over the top reflections were critisised when the addon was released but as usual Devs never listen.
-
I have put them online at dropbox if anyone else wants them
https://www.dropbox.com/s/8fzrzkgl65bnfrh/FT%20phenom%20windscreen_Reflections.zip
-
I have some modified reflection textures, one without reflections but still with the screen heater lines and one with some reflections but much reduced.
PM me your email and I will send them
-
Update
Existing Mouse macros do still work if you copy the macro's over along with the corrosponding sections of the Fsuipc.ini file.
Only the facility to create new macros has gone for now.
-
I would install Prepar3D somewhere other than C:\Program Files (86) if you want to avoid issues with other addons going forward.
Also be aware that while FSUIPC 4.929 and interim 4929C will install and work in P3Dv2.2 there are issues until Peter gets a new version out.
I have found that while 4929C allows me to setup and calibrate my controls it crashes P3D when I try to run Radar Contact and my mouse macros do not work, in fact even the button to create macros has gone from the Fsuipc interface.
Lua frictions are also inop.
No worries though, Peter is back on the 14th so hopefully soon after he will release a fully compatable version
-
Hello Volker,
Many thanks, I am sure you will fix this soon.
-
Hello Volker, that was fast.
In the manual it states that this data is derived from the Navigraph data, but the source really does not matter, it just needs converting to feet, the data appears to be correct just the units used to display it need changing.
Would it not be possible for FSC to do this conversion from miles to feet when the database is converted or by a seperate conversion tool for the msa.fsc file.
Mental arithmetic to convert miles to feet is hard work for me . :smile:
-
Hello
On the FSC map the MSA values are not consistant with what is shown on my Navigraph charts.
What units is FSC using for these altitudes ?
My charts show 7800 as the MSA north of LOWI and FSC shows 14-8 it looks like FSC is showing the MSA's as some fraction of miles and not feet, ie 7800ft = 1.47727 miles
-
1
-
-
Steve and Peter,
Here is an FYI about the freeze-ups on the GoFlight MCP Pro:
I posted this on the GoFlight Forum after talking to their support tech:
http://www.goflighti...pic,1156.0.html
Ohsirus,
Thanks for your quick response.
I just checked with John, the GoFlight Tech, and he confirmed that A25 fixes the freeze problem at the expense of eliminating the serial number. Currently, I'm at version A22 and occasionally have freeze ups, which have been minimized by adding a USB 1.1 card.
Unfortunately, if I update to the latest version now, my MCP Pro will probably no longer work with the Flightsims Lab driver I have for my PMDG 747-400 as there is no serial number with the update. Currently, I've migrated to the PMDG 737NGX which doesn't have software support yet from GoFlight either, although there is someone working on some sort of script file for it.
I saw your response about Flightsim Labs position on this, which is unfortunate. My take on this is that new users who now purchase the MCP Pro (I assume new units are shipping with A25), won't be able to buy the driver from Flighsims lab because it won't work. This would mean no future business opportunities for either the FSX PMDG 747 or the FS9 PMDG 737. Only those prospective customers with older units would be compatible with the driver. So Flightsims lab is shutting out new business opportunities and also prohibiting existing customers who have their MCPPro units upgraded to A25 to fix te freezing issue from using their units with these two PMDG planes.
Bill
Hello
I would forget about waiting for Goflight to support the NGX and use Stephen Munns script instead, works really well here with my MCP
which is Firmware A17.
I am not convinced at all that these lockups are caused by the firmware, I have no issues at all and my firmware revision is ancient.
The MCP seems to be really sensitive to how it is connected to the PC, you are going in the right direction using a USB card rather than MB ports.
Here is what I needed to do in order to get my MCP to play nicely.
Added a Belkin 5 port USB 2.0 card which uses the NEC chip, do not use any card with the VIA chip.
Plugged the MCP into a Belkin F5U021u powered hub dedicated just to the MCP.
The only hubs I have consistent results with are the F5U021u (4port) and the F5U027u (7port) all my Goflight stuff is on these hubs, Max two units per hub with the MCP on its own hub.
No lockups here with A17 since setting it up like this.
Goflight have been saying for years that a firmware update cures all ills with the MCP, they are still saying this and we are now at A25.
I believe that it is more to do with the MCP's power demands and signal path back to the host PC.
And do try Stephens script with the NGX, terrific stuff.
-
Reading1871, thanks for trying to help me.
This is standard procedure for me, always cold and dark, much more fun indeed.
This is the sentence that gave me hope, maybe I have been neglecting this? I just tried it again, unfortunately no result. After using the clickspot the throttles immediately jumped halfway the console.
Your input was highly appreciated though.
Regards,
Ronald
Hello
When starting from cold and dark, at the point where use the clickspot to introduce the fuel my throttle jumps forward halfway.
At this point if you move your physical throttle quickly forward and then fully back the aircrafts throttle moves back to idle.
The aircraft does not jump at this point as the engine is still spooling up and full thrust never has time to happen.
Try it and see if it helps.
-
Hello,
Since I don't get support from Eaglesoft I see this forum as my final resource.
I use FSX on W7-64 with FSUIPC 7.476
Problem is the Eaglesoft Citation X 2.0 which was a great plane in FS9 and 2D
Now I upgraded to the FSX version and VC and can't get the throttle going.
Calibrated in FSUIPC as single throttle, a/c ini file changed for Fadec setting. When I release the throttles from their detent, they jump half way to the fadec cruise position. From there I can move the throttles upwards, but I can never get them to idle.
All other a/c (PMDG, Carenado, default) work fine. FS axis have been eliminated.
I do hope somebody can help me.
Regards,
Ronald
Hello
Use the Citations config panel to set the aircraft up to start as cold and dark, reload the CX then run through the startup sequence.
once the engines are started and the aircraft set up as you like it, save the flight, use that in future alternatively always start cold (much more fun anyway)
One other thing, this CX does not like being loaded after the default flight has been loaded into the Sim, so I always load the CX directly from the freeflight screen, never after a default aircraft.
Also have a look at your throttle axis in the windows calibration axis, any jitter there and all bets are off as far a getting the fadec to work reliably.
-
Hello
As you are probably aware FSCommander currently saves its i-Fly plans into \FSX\iFly\747-400\navdata\fltplan\
The I-Fly 737 needs its plans saved to \FSX\iFly\737NG\navdata\fltplan\
A simple solution with to this problem until the FSC authors patch this behaviour is to create a Junction between the two directories.
In this example my FSX is installed to D:\ drive
MKLINK /J D:\FSX\iFly\737NG\navdata\FLTPLAN\ D:\FSX\iFly\747-400\navdata\fltplan\
FSC will save to \747-400\navdata\fltplan\
The i-Fly FMC coroute option will be redirected to this directory and will see the plan just the same as if you had copied it to \737NG\navdata\FLTPLAN\
Unlike a symbolic link this method also works across network shares.
There is an easy to use tool for those who do not like the CMD line
-
Hello there,
I have a registered FSUIPC which I am not that familiar with yet, so please be gentle when it comes to the technical aspects of using this tool - I am an IRL pilot, but frankly I think it sometimes takes longer to learn how to do stuff in FSX than it does in the real aircraft! I am reasonably technical, but my programming skills aren't up to much and I am not _that_ familiar with FSX (there's a lot to learn!)
I'm using a VRInsight MCP combo panel, I know it normally uses the free FSUIPC but seeing as mine is registered that is presumably what it is using to interface with the sim. I recently purchased it and plan to use it with the new FSX version of the PMDG 737NGX when it comes out, but for now, I am also trying to use it's non-EFIS parts (the radio panel and autopilot controls) with other aircraft in FSX. I've been able to do this with the original FSX aircraft as the SerialFP2 program/driver that comes with the MCP panel seems to interface the hardware with the original planes pretty well.
I am now trying to get the thing working with the JustFlight Beech Duchess and it's not really working out. Autopilot seems to work OK but radio not really. I can make changes to stuff like the NAV and ADF freq's in the FSX virtual cockpit using the mouse and they are reflected in the indications on the MCP combo screen in the radio section, however I can't change stuff on the panel and have it show up in FSX. The one exception to that is COM1 and that doesn't work properly - only the active frequency shows up in FSX properly, not the standby, if I dial a freq on the MCP panel and hit the C/O button the active does get transferred to the active freq in FSX, but the standby freq . It's a Garmin panel in the Justflight Duchess if that helps. There is no profile with SerialFP2 for this plane and googling can't seem to get me anywhere. I am currently using the profile for SerialFP2 that is for the original MSFS planes so perhaps another would work better, but in the list of profiles nothing else seems to fit better (there is nothing for a justflight plane), perhaps someone knows if one of the others happens to work?
I've seen the information about using Lua and VSPE to create custom interfaces between the hardware and different aircraft, but to be honest it seems like a heap of work and I want to be sure that before I start down that route I am doing the right thing and that there isn't a simpler solution. In addition, I'm running Win7 x64 so VSPE is not free on this platform and I don't want to buy it unless I need to (although I might buy it anyway to run my SkyDemon VFR GPS software locally on the FSX PC, instead of over the network using GPSOut over WideFS as I do now).
Can someone point me in the right direction to get this working?
Hello
I had this same problem with the Just Flight Seneca and my goflight units.
For some reason known only to themselves, Just Flight coded their own radios and transponder which have exactly no extra features over the default code, talk about reinventing the wheel.
Due to the modelled 3d knobs in the VC I could not even swap in the defaults.
I had no replys from support on this issue, needless to say it is now deleted and I dare not purchase any more Just Flight aircraft in the future.
-
The Duke uses default MSFS commands for the altitude so there should be no need to use Macros or L:vars in this instance. Macros dont work in the VC by the way, they only work on 2D panels. Do make sure you have the patch for the Duke, the initial release didnt fully work with MSFS commands, the new turbine Duke works perfect straight out of the box.
Hello
Macros work fine for me in the VC, who told you they only work in the 2D panel?
-
I had to send seven e-mails and wait ten days after my original purchase of FlightSim Commander from SimMarket before I had a valid registration to use with FSC. Their support responses to me were originally nonsensical, then condescending, and then just plain incorrect. I spent way too many hours trying to resolve their problem.
It was not just FSC but EVERY purchase I have ever made from SimMarket - always some kind of registration problem!
I would like to upgrade but REFUSE to deal with SimMarket under any conditions
hello
That is really bad luck, I have made 92 purchases from simmarket without one issue yet.
-
Hello
The purpose of this thread is to list the Addons compatible with the Macro facility.
please add to the thread any Aircraft you have found to be fully compatible.
Any additional notes on gauges in the respective panels that do not respond to macro programming would also be helpful
Simcheck Airbus A-300, Totally compatible with macros, all my Goflight units working fine.
-
Hello
In order to keep this thread from becoming cluttered I have started a separate thread concerning Only compatible Addons
-
-
Quality wings 757
-
Hello
No Fsuipc is not the problem.
My advice is to uninstall the Saitek drivers and disable controllers in FSX settings.
Then use Fsuipc to set up your yoke, This is a much better way to go than the crappy Saitek software.
-
Hello Peter
Thanks for the quick reply.
My fault entirely for not reading the documentation, its just after all this time I have committed most of it to memory.
Over the years Fsuipc has probably given me the least problems of anything I have installed on my system.
I have just got into the habit of dropping each new release into /modules without reviewing the docs.
Phenom Hide control yokes?
in Airplanes
Posted
Ralph, you cannot hide the yoke on the Phenom 100 no matter which of the seven OS's or two FS versions you may be running.
D Scobie knows this well enough, I have no idea why he finds it so difficult to answer a straight question.