Flysimware

Commercial Member
  • Content count

    176
  • Joined

  • Last visited

Community Reputation

31 Neutral

About Flysimware

  • Rank
    Member

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes

Profile Information

  • Gender
    Male

Recent Profile Visitors

290 profile views
  1. By hard coding the lights then the fuselage works as a solid polygon to prevent the light from reflecting inside the interior model just like an invisible polygon as you mentioned. So for some reason P3D V4 is no longer stopping light from bleeding effects that are hard coded and this new change upsets me because the hard coding was the trick to stopping any bleeding of light. So i hope someone will pass this info to P3D so they know that some developers hard coded effects so they will not bleed and now your latest version is no longer working. And again this hard coded trick works on all the previous versions. Can anyone confirm that the previous versions of P3D do not bleed with my products?
  2. Thanks for the compliments. I just wanted to let you know that if you open the Aircraft.cfg file and check the fltsim sections we have the manufacturer named as the actual manufacturer and our name Flysimware under the ui_createdby. So i am totally confused by your comment on this topic.
  3. Actually PC Aviator emailed me on the 12th confirming they have updated the last 11 updates. This also includes the C402 V2.3 to V2.3a. I have no control when a store updates but we do send then the updated products at the same time.
  4. Here is a secret about beacon and strobe lights. Most developers create these using the aircraft.cfg file and this causes the lights to reflect inside the interior model depending on the distance and location. So right below the pilot seat is the worst. Some popular sim Company's i won't mention have posted this is normal for FSX and P3D and there is no fix. I agree as long as your using the config to create lights. But there is a solution. If you hard code those 2 lights in the exterior model and do not use the config file then they will not reflect on the interior parts. i do this for all of my aircraft and it works for both FSX and P3D. So i did a test today and all the aircraft in P3D V4 all do the same but the beacon is not close to the VC. And i find that this latest version is not working with my method. So i can only blame P3D V4 for changing the lighting. I tried to turn on receive check box for interior and the walls stopped reflecting but all my parts with reflective shine still continued to flash from the beacon. So for now there is no fix until P3D V4 gives the public a reason why it now reflects this lights when hard coded. So until i learn of a fix this is considered normal by most developers.
  5. Logic says if our GNS 530 works in FSX, FSX:SE and P3D then it works for all of the sims we make the aircraft for. And if it's working in your FSX sim and not your P3D then the logic is that there is something wrong with your P3D. Although it is odd how you could prevent this from working but i would bet if you had a fresh install of P3D and our aircraft there would be no issues. This is why i asked you to go from our email customer support to this thread so maybe someone can explain why this issue could happen. By the way the radar zip file is not on the payware aircraft page but on the C402 product page where you can download the manuals and read the updates. And this has nothing to do with the GPS. It's to bring the radar to life if you do not own the payware Rex radar by Milviz.
  6. Was this after a fresh install and no changes? Because so far no issues have been reported. And glad you opened this thread as i suggested so we can figure this out. I only suggested this zip file if you want to use another radar that we have setups for. The main radar is payware and you must own it. The zip files is located on the main website product page.
  7. Try un installing then make sure the aircraft folder is deleted. Now install a fresh copy then test from there. Now since we changed some of the model folder names and panel names you need to add your info into our new config files and not use your old ones. That is your issue in my mind. Please get back to us and thanks for adding this topic as i suggested so other can also avoid these issues.
  8. Ark is planing on using his code he wrote to input any value from your keyboard. But if you look at the last line of code i sent you there is a separate rule that tells the custom value to be sent to the default value. If ALT/SEL mode is off then there is another hidden logic code that tells the default to be zero so the aircraft will not capture any value in the alerter. So we only want the custom input from your keyboard to work if the conditions are right so there is not a conflict flooding in the background. Which i think Ark's is doing if you use it with AlT/SEL off. So we are going to improve Ark's code tomorrow and he will share it here once done.
  9. The autopilot code for the Cessna 441 is default. I don't have any code. So for it to not hold altitude based on the ALT ALERTER. does not make sense. I also can't find any issues when i test it. Is there anyone else that is having no issues?
  10. Now that i have the new 64bit sound module from the original developer i can make new installers for P3D V4. So far 8 projects are done and the second set will be the last 10 projects that use DLL's since V4 requires 64bit DLL's. All but the Lear35A will work without the sound module as you will only be missing a few bonus sounds like switches. I will take a look at the low altitude hold issue today.
  11. P3D V4 update info: Until we release updated installers for our products the installer can still be used to install to V4 by selecting the V3 option. Then change the destination. More info about using the older installer is on our help page. Visit our main website product page to find out what DLL's you need to update your product. Most products will work now in V4 with no bonus sounds. But the Lear35 needs the fuel dump DLL to make this product work in V4. The payload manager DLL is ready and we are waiting for the sound module and the fuel dump DLL to be updated by the developers. This may take up to a few months. Sorry for the wait but the DLL's we do not develop ourselves and must wait just like you are. I spoke to both developers and they do plan to update the DLL's which need to be 64 bit which is not an easy update.
  12. We appreciate all the support that was reflected in this thread. As i stated our product does not alter any sim files or effect how your sim continues to work/ The sim may vary on the performance during the use of our product but does not cause any destruction to your sim.
  13. For P3D V4 updates Flysimware only has to update 2 files for those users. We will supply those files on the main website product page when they are ready. The installers will stay the same and any V4 customer will have to download to get those DLL's. In our future updates we will include a V4 option to install that will use the correct DLL's. But until then you will have to download. Payload manager DLL for 64 bit is available now. Custom sound module DLL for 64 bit is not available yet. But is getting updated. =============== For the cabin light effect that was mentioned in this topic this is working and there is no reason for it to not work in V4. Check that the effect is in the effects folder.
  14. For P3D V4 updates Flysimware only has to update 2 files for those users. We will supply those files on the main website product page when they are ready. Payload manager DLL for 64 bit is available now. Custom sound module DLL for 64 bit is not available yet. But is getting updated. =============== For the cabin light effect that was mentioned in this topic this is working and there is no reason for it to not work in V4. Check that the effect is in the effects folder.
  15. According to the majority of our customer on FB on the topic P3D V4 they all say everything works using 64 bit V4. Did you copy the aircraft to V4? That would cause the issues you mentioned. I have instructions on our main website help page on how to install to V4 using the installer.