• Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. BusheFlyer

    Best uk/Western Europe scenery for P3D V4.2

    I am using the Horizon Gen-X VFR photoscenery with ES trees in 4.2 along with UK2000 airports. Whilst the Orbx stuff looks 'prettier' it just doesn't compare to actual photo scenery. I guess if you like doing VFR flying then thats the best there is, if your interest is the big jets then Orbx England/Wales/Scotland will look better and the lack of accuracy won't really concern you.
  2. BusheFlyer

    Default AI Airraf are Back

    To answer your question, the solution is very simple. Look in your prepar3d installation directory at the following path: X:\Prepar3d\Scenery\World\scenery and locate the trafficAircraft.bgl file. This is the default AI aircraft. Simply either delete it permanently or rename it to trafficAircraft.bgl.BAK.
  3. BusheFlyer

    P3D 4.2 - Anything Incompatible?

    Flight1 GTN 750/650 (Complete) has now been updated to P3D 4.2.
  4. Thank you for posting this, co-incidentally I have spent the past two days periodically converting AIA/TFS and other AI models to P3D4.0 in order to correct the scripting content errors so have now gone through and ensured everything had a radio section.
  5. BusheFlyer

    ASCA vs Soft Clouds

    Well if you mean that REX copied the leading product (FEX) which still today has the better quality and variation of cloud/water/sky textures. What REX have been good at is marketing. Don't take my word for it, look at the alpha channels (which is what defines the cloud quality) compared with FEX.
  6. BusheFlyer

    is P3D V4 more of a GAME than any other ( sim )

    I think Flight Sim's in general could be categorised into many things depending on what the user does with it. Everything from a hobby through to an occasional time waster (video game), to a learning and educational tool. Also whilst things like grass, and sloped runways would be nice, they are by no means a show stopper for a simulator. Besides you have to consider what you are asking.. let me give you a real world example: Many soft field runways in the real world, particularly for farm strips and even some widely known airports (EGHA for example) have variable soft field conditions. Often a prior call to a farm strip or EGHA will result in instructions like "please land to the right side of the runway to avoid the muddy area on the left side". So how do you model in this in the sim? Lets suppose the sim models soft field conditions of long grass/short grass, to be actually realistic it would also need to model whether it is wet or dry and also how boggy (or not) the soil is. Some grass strips are plain unusable after periods of rain to nose pushers. What I am saying is, your asking for a can of worms to be opened. Flightsim's should of course be as accurate as possible.. however when you get to the finer detail then it will likely always fall short.
  7. BusheFlyer

    JustFlight PA-28R Arrow released

    Excellent, a C150/152 to the same high standard would be great. Other wishes from the Cessna range would be the C180 (whilst not as comfortable as the C182.. it beats a nose pusher for those tricky grass strips, as well as has the smooth continental).
  8. Interested to hear if anyone has managed to get P3D V4 to display any textures in BC7 format? I have converted some aircraft textures to BC7.. they look absolutely perfect in a Direct Draw window, exactly the same as DXT5 (with obviously the higher quality). Use it in P3D and black texture. The same base uncompressed bitmap was used with exactly the same format. Into BC3 (DXT5) it works fine.. BC7 nope. Slightly disappointing because the quality of BC7 is indistinguishable from the base bitmap, DXT5 has all the usual artifacts. If we could use BC7 we would get bitmap quality at DXT5 filesize.
  9. BusheFlyer

    RealAir Turbine Duke V2 in Prepar3d V4

    That would be great! Many thanks for looking at it.
  10. BusheFlyer

    RealAir Turbine Duke V2 in Prepar3d V4

    The file name to replace is: RASDukeTv2_Sound.gau The panel.cfg shows: gauge21=RASDukeTv2_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Duke Turbine V2/Panel/Sound/RASDukeTv2_Sound.ini Many thanks for this Doug. May I also ask, I and I suspect many others use the now unsupported Baytower Vans RV7 which I believe also includes some of your work: btsENG.dll which according to the details was originally named: dsd_wastegate_control.dll with your name as the signer and author. Do you have any plans to update that dll also to X64 at all? Warm regards
  11. Just a FYI. I installed Super Cub X from FSAddons into the Prepar3D v4 Add-ons directory and added an appropriate add-on.xml file and all works without any changes in P3D 4.0. I like this addon purely because of the variation of models you get.. the flight model is not the best and neither are the VC graphics however it's nice to fly around with tundra tyres or skis. No issues were found, all gauges and sound work as it is a relatively basic aircraft. FYI here is the add-on.xml file contents: <SimBase.Document Type="AddOnXml" version="4,0" id="add-on"> <AddOn.Name>FSAddon Super Cub X</AddOn.Name> <AddOn.Description>FSAddon Aircraft Super Cub X.</AddOn.Description> <AddOn.Component> <Category>SimObjects</Category> <Path>SimObjects\Airplanes</Path> </AddOn.Component> </SimBase.Document>
  12. BusheFlyer

    Add-ons at risk

    Superb! Nice work Bert! Glad you made sense of it. I just tested and working here also. Fantastic, it's nice that this fine aeroplane can live another life in P3D 4.0.
  13. BusheFlyer

    Add-ons at risk

    Yeah I feel there is.. essentially it's one function that is causing the issues with the transponder. Problem I have is LUA to me is so damn awkward to actually read. Perhaps a LUA expert might be able to spot what this issue is with this macro: <!-- Procedure: Numerics, compare button press against screen address (@1;number, @2-@11;screenAddress) --> <Macro Name="keyTest"> @2 if{ 0 (@xpdrCrsr) == if{ @1 (&gt;@adrs0) 1 (&gt;@xpdrCrsrIncr) (@xSquawk) (&gt;@xPrvSquawk) } } @3 if{ 1 (@xpdrCrsr) == if{ @1 (&gt;@adrs1) 1 (&gt;@xpdrCrsrIncr) } } @4 if{ 2 (@xpdrCrsr) == if{ @1 (&gt;@adrs2) 1 (&gt;@xpdrCrsrIncr) } } @5 if{ 3 (@xpdrCrsr) == if{ @1 (&gt;@adrs3) 1 (&gt;@xpdrCrsrIncr) @clrTimerSet } } @6 if{ 4 (@xpdrCrsr) == if{ @1 (&gt;@adrs4) 2 (&gt;@xpdrCrsrIncr) } } @7 if{ 5 (@xpdrCrsr) == if{ @1 (&gt;@adrs5) 2 (&gt;@xpdrCrsrIncr) } } @8 if{ 6 (@xpdrCrsr) == if{ @1 (&gt;@adrs6) 2 (&gt;@xpdrCrsrIncr) } } @9 if{ 7 (@xpdrCrsr) == if{ @1 (&gt;@adrs7) 2 (&gt;@xpdrCrsrIncr) } } @10 if{ 8 (@xpdrCrsr) == if{ @1 (&gt;@adrs8) 2 (&gt;@xpdrCrsrIncr) } } @11 if{ 9 (@xpdrCrsr) == if{ @1 (&gt;@adrs9) 2 (&gt;@xpdrCrsrIncr) } } </Macro> I am currently looking for another example of translating the transponder numerical keys to the display so I can perhaps make some sense of it.
  14. BusheFlyer

    Add-ons at risk

    I have it working also, rather than disabling the transponder I edited the gtx327.xml file in the btsRV7.CAB file and it works. The edited bit is the part that is causing the crash with the transponder: <!-- numeric button actions --> (@xpdrMode) @mdTest &gt; if{ <!-- @zero (@xpdrKey) == (@K0) ! and if{ @keyTest(0.000001, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1) @keyAction } @one (@xpdrKey) == (@K1) ! and if{ @keyTest(1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1) @keyAction } @two (@xpdrKey) == (@K2) ! and if{ @keyTest(2, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1) @keyAction } @three (@xpdrKey) == (@K3) ! and if{ @keyTest(3, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1) @keyAction } @four (@xpdrKey) == (@K4) ! and if{ @keyTest(4, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1) @keyAction } @five (@xpdrKey) == (@K5) ! and if{ @keyTest(5, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1) @keyAction } @six (@xpdrKey) == (@K6) ! and if{ @keyTest(6, 1, 1, 1, 1, 1, 1, 0, 1, 0, 1) @keyAction } @seven (@xpdrKey) == (@K7) ! and if{ @keyTest(7, 1, 1, 1, 1, 1, 1, 0, 1, 0, 1) @keyAction } @eight (@xpdrKey) == (@K8) ! and if{ @keyTest(8, 0, 0, 0, 0, 1, 1, 0, 1, 0, 1) @keyAction } @nine (@xpdrKey) == (@K9) ! and if{ @keyTest(9, 0, 0, 0, 0, 1, 1, 0, 1, 0, 1) @keyAction } --> } This case in the Update function refers to a keyTest macro in the same file. Any call to that leads to the crash. As to why it is crashing.. I have no idea.. the abomination that is LUA makes it very hard to follow or debug. Anyway, commenting that out makes the original transponder work except for the manual entry buttons, all other functions work perfectly.
  15. BusheFlyer

    few more A2A installers just released for v4

    Well honestly I don't see much difference between the vertical stability between real life and the sim, in real life if you nudge the stick back and then let go it will climb for a time until the loss in airspeed causes it to descend and it will oscillate like that until it stabilises at the trimmed airspeed. The same is true in the sim, as long as it is trimmed for cruise it will bounce around a bit both naturally and by pilot inputs but will eventually settle back at the trimmed airspeed. However, trimming is definitely harder in the sim than real life, simply because you can't 'feel' it. So no dispute there.