Jump to content

FlyAgi

Developer
  • Content Count

    47
  • Joined

  • Last visited

  • Days Won

    4

FlyAgi last won the day on May 18 2019

FlyAgi had the most liked content!

Community Reputation

29 Excellent

3 Followers

About FlyAgi

Recent Profile Visitors

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

  1. 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.
  2. 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.
  3. Without a complete log.txt I can't do anything.
  4. The winter works for ortho but you have to modify the ortho tiles: Tutorial - SAM Seasons with Ortho4xp and Winterizer
  5. Some notes I posted over on the org to minimize confusion about the seasons library: Installation works as following: Download and extract SAM_Seasons package Place SAM_Seasons into Custom Scenery Check if 'library.txt' is present inside SAM_Seasons (if this is true it will work) Install latest SAM v2 plugin Now the seasons should technically work fine but you have to care for some things: Place SAM_Seasons on top of Scenery_packs.ini (really, it's important to avoid lots of conflicts with other replacement libraries) Don't place additional Tree packages (MisterX HD Forests, FlyAgi vegetation Global Trees, TerraFlora) above SAM_Seasons When using SFD Global place SFD Global below SAM_Seasons in Scenery_Packs.ini (switch off any season to get SFD Global summer) When using TerraFlora place TerraFlora below SAM_Seasons in Scenery_Packs.ini (switch off any season to get default summer with TerraFlora trees) X-Europe 3 is not yet supporting SAM_Seasons, I'm currently working to fix this for the next X-Europe update (coming soon, really) If you are using FlyAgi Vegetation and/or Global Trees please update to the latest versions Ortho4xp tiles have to be modified (technically this is possible but this requires lots of space and some work to do for the user) to support seasons, the library can't do this for you - for now switch off your Orthos when you want to fly in winter Orbx TrueEarth is not supporting SAM Seasons for technical reasons, they would need to ship seasonal textures with their sceneries to make this work The menu 'Colors + Seasons' works as following: For now ignore the left part 'Colors', this is not important for the seasons library The right part 'Seasons' is controlling the seasonal library If every season is siwtched off (nothing is higlighted in blue) the seasonal library is inactive, you will the see default scenery with default trees or any other scenery replacement like SFD Global, TerraFlora, MisterX HD Forest and so on (once again, place SAM_Season on top of scenery_packs.ini if this is not true) If you want whiter trees in deep winter season click on the settings icon next to 'seasons' and switch on the snowy trees - this requires a scenery reload to be visible All settings are stored so when you come back to the sim you will see the season which was active when you left SAM Seasons works scenery based so it's replacing default scenery with different color corrected versions based on season active (pretty much like TerraMaxx or WinterMod are working). For now there is no support for automated seasonal changes based on different conditions, this was talked about but I don't know when this will be implemented. SAM Seasons is intended to be used as an alternative to Wintermod and TerraMaxx because the first one is a bit complicated to use (even with JSGME) and the second one seems to be not that wide spread as desired so almost no designer supports it. I hope I did not miss anything important but if so just tell me.
  6. 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)?
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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 startup and this is only needed to activate some changes so as long as you don't change parameters in the GUI there is no need to do this. Regards, Agi
  14. 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