Jump to content

FlyAgi

Developer
  • Content Count

    59
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by FlyAgi

  1. I'm not sure if they run together but it makes no sense to run FTU with 3jfps together as they are doing about the same things, if you run FTU and enable autolod you don't need 3jfps.
  2. As far as I know this is an issue related to some aircraft plugins not working right in 11.50. Maybe updating either those aircrafts or flywithlua might help.
  3. There is no need for such a script which changes water parameters with wind changes, this is all done by X-Plane automatically with standard real weather, FSGRW or ASXP. If you want parameters from a certain static water script I recommend to dial in these values into the FTU water menu which should then give you the same results. You can then save the values to a file with the load/save button, configure another water script, save this one to another file and after that you can simply load any off these files on the fly in the water menu. If your water script is a dynamic script and not
  4. No, the presets are designed to work stand alone without anything else but you can also try to use them in combination. If you want the full cloud art as designed by the author you have to put the lines of the script into the FlyAgi_Tweak_Utility_Static_Override.lua in between the marked blocks so it will override FTU settings at launch. Then in FTU set the advanced clouds to 'Default', disable Auto Clouds Lighting and Cloud Level Fix and reload everything by reloading all lua scripts. Now you should have overriden FTU Clouds completely with the cloud art parameters. The static overr
  5. I'm currently not planning to bring back shadows manipulation as most of the DataRefs are useless in 11.50 anyway and I don't want to add a new menu with just one option to manipulate scenery shadow distance. If you want to set them automatically at startup just use the following lines in a new and empty script (a text file renamed to .lua): set("sim/private/controls/shadow/csm/far_limit_exterior", 2000) set("sim/private/controls/shadow/csm/far_limit_interior", 2000)
  6. You can attach a log.txt file to the messages by just dragging it or use the 'choose files' button. Anyway, the latest version (1.13a) possibly fixes this as there is no aircraft settings file any more so please download and try the latest version.
  7. Copy Resources into your X-Plane root folder as stated in the manual.
  8. The HUD module test script is incompatible it seems. Asthereare lots of compatiblity issues because of dataref access conflicts I can't fix them all easily but have to rewrite the whole thing. I'm planning to do this step by step but this will not happen anytime soon, next step will be removing some non-essential features and decreasing the need for datarefs as well as code complexity to reduce compatibility conflicts but I can't say when I get this done right now.
  9. The intensity is the strength for lod reduction, higher values mean faster fps recovery but also less objects visible. The value is indepent from the target fps setting, increase intensity to get more stable fps or decrease if lod is too low (not enough objects visible) most of the time.
  10. This sets the lod to maintain target fps as set in the target fps button. If fps fall below thespecified target, objects visibility range is reduced to recover fps.
  11. Copy the following files and folders from the zip archive into X-Plane 11/Resources/plugins/FlyWithLua/Scripts: FlyAgi_Tweak_Utility (folder) FlyAgi_Tweak_Utility.lua FlyAgi_Tweak_Utility_Static_Override.lua Then start X-Plane and the utility will show up. :-)
  12. Do the following: Copy the folder SAM_Seasons_SDK and the library.txt file you find inside the main SAM_Seasons_SDK folder into your Scenery If you already have a library.txt copy the contents from the one provided by the package except the header (A 800 Library) into your library.txt To get an independent library (recommended for payware or if you want to make changes to the SDK assets) open library.txt with a texteditor and search for the line "# export path is SAM_Library/SAM_Seasons_SDK/..." Replace "SAM_Library/SAM_Seasons_SDK/" with "My_Unique_Scenery_Name/SAM_Sea
  13. This is a compatibility problem with other scripts - you will have to remove them or rename their datarefs so they match the FTU datarefs names.
  14. Without a complete log.txt I can't do anything.
  15. Glad to hear - may I ask you what framerates you get when this happens? And, if this happens once gain, could you please check in the launcher options if the 'global settings' save file has been loaded properly (before reloading the scripts)?
  16. The messages should disappear by themselves once the save files have been loaded properly. If the don't disappear I think there is something messed up with the save files. When this happens try a scripts reload (XP header bar > FlyWithLua > Reload all scripts), this should solve the issue for this session. I experienced something like this myself but only once and only with exccessive testing some stuff, loading and changing aircraft and if this is done too fast the save files writing and loading can get currupted - this is why the message actually exists, this is for making sure the use
  17. In Atmosphere + Visibility check the DSF visibility buttons and set them to default values: min 20.000, max 100.000 This is the only utility setting affecting the lights because the lights depend on the DSFs to be drawn.
  18. Actually the utility should not do anything to the lights but I can imagine this could have something to do with the lod control. If this is true setting fixed and higher lod values (this means no auto LOD) should solve your problem. If this does not solve your lights issue pklease report back so I can have a look into it.
  19. That's fine and I think you have some interesting points to tell. If you still want to develop for X-Plane I suggest to just grab a project and start doing it. I did never do any programming before and made the utility while I learned the basic lua it needed and designing sceneries as well I learned by doing and all this startet about 2 years ago - at the beginning of 2017 I had absolutely no clue about anything X-Plane as I just switched from P3D some months before. X-Plane however was very different to me, it made me create some gateway airports (I was never interested in creating any
  20. I've been reluctant to fly in XP11 so many times... then I started tweaking and then made the utility. With some lua knowledge from the utility work I can now fix almost everything so XP11 is finally fun and possibly problems can be solved easily.
  21. Great to see someone who benefits from the controller options - I made this originally with my quite sluggish xbox 360 gamepad in mind and I needed nullzones and a mnual calibration to get this working properly. This all ended up with me flying helicopters with a gamepad, no stabilization of course but proper setup.
  22. Hi Adam, you can find the most recent information on my website, there is also a changelog giving some hints on new stuff when introduced: FlyAgi Tweak Utility Regarding the hot keys: There are many hotkeys available for most important things (in the X-Plane keyboard/joystick menu) but the weather reload can be handled with a native X-Plane hot key, look for 'regenerate weather' in the key configuration (the tweak utility triggers this command to redraw the clouds). If you have set up everything you don't need to redraw the weather btw, the utility does this automatically after
  23. The X-Visibility menu is now named 'Atmosphere + Visibility'. In there you find all the X-Visibility controls as before, the menu has just another name and has more atmosphere related options now.
×
×
  • Create New...

Important Information

Please read the Terms of Use