Jump to content

FlyAgi

Developer
  • Content Count

    54
  • Joined

  • Last visited

  • Days Won

    4

FlyAgi last won the day on May 18 2019

FlyAgi had the most liked content!

Community Reputation

30 Excellent

3 Followers

About FlyAgi

Recent Profile Visitors

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

  1. 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.
  2. Copy Resources into your X-Plane root folder as stated in the manual.
  3. 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.
  4. 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.
  5. 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.
  6. 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. :-)
  7. 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_Seasons_SDK/" for all occurances (results could look like "AS_EDLP/SAM_Seasons_SDK/" for Aerosoft Paderborn) Now you have an exclusive library for your scenery only and can place all the contents from the path "My_Unique_Scenery_Name/SAM_Seasons_SDK/" in WED You can also modifiy all SDK contents without braking other sceneries as long as you are using your own library path To get seasonal changes you have to use a library and musst not place the assets from the local path in WED. If you already have placed lots of stuff you can simply change resources in WED so you don't have to start from scratch. If you don't want to ship the SDK you can also use it as a normal library. In this case just copy SAM_Seasons_SDK into your Custom Scenery folder and place assets from "SAM_Library/SAM_SEasons_SDK/" path. Of course, users then need the SDK installed as a library themselves - I recommend this if your scenery is already depending on lots of libraries so one more or less does not really matter.
  8. 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.
  9. Without a complete log.txt I can't do anything.
  10. 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)?
  11. 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 user waits for the utility too finish loading before doing anything. If lua scripts reload does not work try deleting the save files for the aircraft affected by this issue and try again - the message should disappear if the save files are okay.
  12. 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.
  13. 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.
  14. 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 anything for FSX or P3D) and soon after I was creating full custom sceneries and then some simple lua tewaking here and there and it all added up, step by step. X-Plane is really developer friendly, you can just start doing as the most important tools are provided and documentation is also pretty good for the most part - all you need is a project to start with and, maybe, some people to work with. I can't tell you much about aircraft design (modelling part) but if you, for example, want to create custom systems you could start with an aircraft available which does lack in the systems department and create some systems yourself with lua (xlua, FlyWithLua, SASL). I'm doing this myself for some parts of the utility, the force trim and other helicopter stuff are in fact custom systems which can be added to helicopters (I made xlua versions as well). If you don't want to do the modelling but more the systems part I think this is a chance for you as many aircraft come with great modelling and all this but they often are limited in the curstom features and systems department - so if you can do this it should be easy to find a developer to team up some day. Well... thank you very much, Adam. To see that others like my work is the biggest reward I can get and this is also what makes me keeping on.
×
×
  • Create New...

Important Information

Please read the Terms of Use