Jump to content
The simFlight Network Forums

canadagoose1

Members
  • Content Count

    95
  • Joined

  • Last visited

Community Reputation

2 Neutral

About canadagoose1

  • Rank
    Advanced Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Not Telling
  • Location
    CYYZ

Recent Profile Visitors

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

  1. Yes, I am actually using 2048 x 2048. Don't notice much difference. I only replaced the "emb_glarebuttons.dds" file. I left the "emb_glarebuttons_n.dds" as is @ 1024 x 1024 because I noticed a bit of a stutter using the 2048 or 4096 size. But you can try the 4096 and see for yourself.
  2. OK, I fixed it! There is a .dds conversion app online (https://www.aconvert.com/). I used it to re-size the "emb_glarebuttons.dds & emb_glarebuttons_n.dds" files to 2048 and 4096. I tried both the 2048 and 4096 and didn't see much difference in resolution. So I settled for the 4096 (no hit on FPS either). The Glareshield buttons are readable from my normal VC view now. It's like night and day! I am keeping the 3 options (1024, 2048, 4096) for these 2 files in a separate folder for backup in my "sharedtexture" folder in the feelthere PIC E175 folder. They can be easily interchanged if needed. Sorry, the converted file zip would total 17mb, the max for attachments is 4.88mb, so I am not able to include them here. But the above files are easily converted using the website above. Hope this helps others with this problem. Regards, TS
  3. Because it is the "Glareshield" buttons I am having the problem with, I opened the "sharedtextures" folder in the PIC E175 folder and there is a file called "emb_glarebuttons.dds" with a texture size of 1024 x 1024 pixels. If that file size was changed to say 2048 or 4096 (If I knew how to do that I would give it a try...Maybe there is a file conversion app out there), would that possibly fix the problem? Maybe the developers could chime in here as well. But maybe it's not as easy as that. I don't know. Regards, TS
  4. I thought the blurry MCP texture problem was fixed in the latest Service Pack. I did a flight today and it was impossible to read the buttons on the MCP. Even when I zoom in they are hard to read. I can easily navigate the various buttons by memory, but that is not the point, I'm Lazy...LOL😀. They should be more legible than currently presented. I believe this was one of the top of the list features that needed to be addressed with the latest Service Pack. Has anyone else experienced this with the latest build? Regards, TS
  5. I installed the normal way and then manually moved the Feelthere folder O/S of the root P3Dv4.5 drive. It's over 10gb, I do not want it taking up space on my SSD drive. So I created an addon.xml file with the following and placed it in documents\Prepar3D v4 Add-ons\FeelThere Ejets : <?xml version="1.0" encoding="utf-8"?> <SimBase.Document Type="AddOnXml" version="4,0" id="add-on"> <AddOn.Name>FeelThere EJets</AddOn.Name> <AddOn.Description>FeelThere EJets</AddOn.Description> <AddOn.Component> <Category>SimObjects</Category> <Path>D:\P3D v4 Addons\FeelThere EJets\SimObjects\Airplanes</Path> </AddOn.Component> <AddOn.Component> <Category>Scripts</Category> <Path>D:\P3D v4 Addons\FeelThere EJets\Scripts</Path> </AddOn.Component> <AddOn.Component> <Category>Effects</Category> <Path>D:\P3D v4 Addons\FeelThere EJets\Effects</Path> </AddOn.Component> </SimBase.Document> Everything works fine. Regards
  6. I think I have resolved my problem. When I ran the Installation file it gave me 2 choices: 1. Install Into prepared 3Dv4 folder OR 2. Install Into prepared 3Dv4 User Add-ons folder (which installs to the Document folder on the drive P3D is on) I should have used #2... to install into Add-On folder, which I have now done and I moved the FeelThere Ejets folder over to my D:\ drive and placed an xml file in the Documents folder to point to that Drive. So, the Configuration file seems to be working now. Thanks for your assistance and time! Regards, TS
  7. BTW, can I install directly (or change the installation location) to a drive outside of the P3D drive?
  8. Yes, I uninstalled the Original but did not run the SP1 Installer as Administrator. I moved the Feelthere Ejets folder to my D:\ drive and pointed to it using the P3D addon xml procedure. This is how I did it with the 1st release with no problems. Thanks for the reply.
  9. When I click on the Configuration extension file it does not recognized my E175 and E195. The tabs are greyed out across the top. Any ideas? BTW I have the latest installation file. Regards TS
  10. Sorry everyone, but I do not see this issue listed under the "KNOWN ISSUES ON THE EMB V3" post.
  11. This is to confirm that my Upgrade purchase was in fact successful using my previous v2 installation file ( ejetsv2-p3dv4-3.exe ) KEY code. On installation of the new v3 product the pop up box asking for my previous key code was already populated with my key code. I am happy to report it was a flawless installation. So, if anyone has the same v2 installation file as me, I am confident the key code most likely does work.
  12. Thanks for chiming in on this. I of course have the same version file. I am not sure when I purchased my version but It was through Feelthere as well. Nice to see I am not the only one. Regards
  13. Sorry to keep this going, but I was browsing the AVSIM forum on the subject and I came across this thread: https://www.avsim.com/forums/topic/551328-feelthere-developing-new-ejets-for-p3d-44/page/11/ About 2/3 down on this page someone asked the same question I did regarding the ejetsv2-p3dv4-3.exe file I have. The next thread answered "YES", that in fact the product key for that purchase did work. I think they are the same files, the only difference being one is for P3D version 4.1 and the other P3D version 4.3 (representing a service pack that was issued by Feelthere). I may be wrong, but it does look like the product page description could be confusing to potential customers like myself. Should it not be amended to include the file "ejetsv2-p3dv4-3.exe"? Maybe I can send you my product key and you can confirm to me whether it is valid or not? Regards
  14. Fair enough, but...Irregardless of the fact that your file and my file are both execution files for the same thing. Both are, I assume, versions of the same files for P3D compatibility. To me, the .exe file I was sent when I purchased the v2 P3D port over should be the same as the arbitrary file name you mention in the product description. I do not know why they would be different. In any event, I appreciate the fact that you have upgraded to version v3 and look forward to your getting the reported bugs fixed, at which time I will reconsider my purchase. Regards
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.