Jump to content

cardajowol

Developer
  • Posts

    206
  • Joined

  • Last visited

  • Days Won

    91

Everything posted by cardajowol

  1. Visual changes/object additions have no impact to FM or Systems. The only impact that has to systems is editing the ACF which is done yourself. If do not incorrectly can affect systems. Currently this mod has not been tested with XP12.
  2. I have no reason for why it does that I have tried to resave it same thing happens, only gimp that has a problem works fine in Photoshop.
  3. This is likely due to a change made by toliss in an update along the road, it will get amended on next update of the LEAP.
  4. the mod is purely visual, if your getting error messages and green screens, its either a corrupted copy you've made or you've changed something in the ACF you shouldn't of, names, addition information in the authors section.
  5. You've not removed part of one of the objects, you'll need to go over that part of the manual again.
  6. What are you trying to remove it from as its not on the engine mod for the 320.
  7. Fan Spin, is likely something Toliss changed on their end in the coding, may have flipped the direction. It may get updated in the future, not had time to look in to new updates at the moment. Hopefully soon.
  8. you can not using the NEO and CEO on the same install for the 319, they do not have NEO options provided by Toliss to override.
  9. You haven't, go recheck the manual, make sure you properly check the kill data ref entries make sure they match and there is no spaces in them before or after. Also make sure to used the correct engine objects for the 321/319, they need to be out of the specific pack, you can't use the 319 on the 321. and visa versa
  10. You probably don't have the N1 object added last in the order in plane maker.
  11. No optical issue there, you just plainly have 2 engines over the top of each other. You might want to refer back to the manual check you've removed the default engines correctly.
  12. FF liveries would of had AO where the old engine used to be, that is what this is, unless you are using a livery that was made specifically with my engine your gonna get that AO on the wing. (AO = Ambient Occlusion [like a shadow])
  13. makes no difference no explanation required just copy it in to the plugins folder of the plane, its mostly self explanatory .
  14. check your coordinates likely incorrect, especially the 2nd one check you've not missed any "-" signs, either that or you have an issue with the kill data ref you've used.
  15. you've not done the kill data ref correctly in plane maker go over it again re-read the manual, check for errors in the text and possible spaces you've added to beginning of after the text in the kill data ref.
  16. You don't need to delete the engine textures in the base objects folder, the folder structure is listed in the manual further towards the end. If you need some help look at A320 liveries that include my engines as to the folder structure, the provided liveries in the pack also includes the correct folder structure with in the livery.
  17. There is only 1 reason to leave the objects is if you are looking to use 1 of the default engines with 1 of the engine mods, if you are replacing both or just having separate installs for each engine mod then you do not need the objects.
  18. If this is the A321, you need to go back check plane maker and check you put the correct datarefs in the killdata ref entry as stated in the manual. You also want to make sure your using the engine objects from the 321 zip pack not copied from the 319.
  19. The chevrons are livery based, you'll need to make your own that remove them or use a livery that has done that for you.
  20. The manual was wrote before the CFM so has no requirement to remove the blades/engines in it, if you read the CFM manual its in there. I know whats in the manual I wrote it.
  21. ? There is an override for the toliss particles to lower some values for performance and there is 1 custom particle I included. In the pack the CFM one, that should only be used when using the engine stand alone and not with the IAE mod.
  22. Youve either changed the name of the ACF or something in the Authors section of the ACF that the plugin needs to function. Or your copy of the 320 was corrupted. You'll have to start again. Copy the FF320 folder load it up first check it works then do the mod. But don't change the file name of the acf or anything but the UI name of the authors panel. Thats the first box at the top.
  23. The mod is purely visual, it doesn't not affect betterpushback, if its not working its because you changed something in the ACF you shouldn't have fields in the author panel or the name of the ACF. there is nothing else that would impact that.
  24. Sounds like an xplane issue, like I said try in cavok conditions, check your settings. If its doing it to different things including the fuselage not an issue with the mod.
×
×
  • Create New...

Important Information

Please read the Terms of Use