mikeymike

Zspd imaginesim for P3d v4

Recommended Posts

I have posted on another thread with no answer.

i would to purchase zspd 

so I thought ide start my own

i have read and also seen on YouTube Video that zspd imaginesim P3d v4 that there is texture bleeding and overlapping 

only around the outer perimeter of scenery.

is it compatible with envtex orbx vector or global

thanks in advance 

mike

Edited by mikeymike

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

I have this scenery, as well as FTX Global and Vector, i do not recall any texture bleeding issues on my setup.

Share this post


Link to post

I have the scenery and I always had some strange water bleeding through the scenery around the north eastern part of the scenery. Discussed for ages with Imaginesim already for the FSX version, they never solved this. Currently, the scenery is not installed anymore, I would love to know if this issue still persists, but as I was one of the only few having this bug, I doubt anyone can tell me...

Share this post


Link to post

I have the P3Dv4 version (just recently updated by Imaginesim within the last week) and I am parked at D73 right now to do LH729 to EDDF with the 748 and I have just checked and no issues as described above.

I have FTX Global, Vector, Pilot’s Mesh 2018 and all good.

Edited by mwa05

Share this post


Link to post

I owned the FSX version and now the P3D and I remember the issues you describe, but a major update in March fixed them. It also dramatically improved performance, at least in P3D.

Share this post


Link to post
2 hours ago, mwa05 said:

I have the P3Dv4 version (just recently updated by Imaginesim within the last week) and I am parked at D73 right now to do LH729 to EDDF with the 748 and I have just checked and no issues as described above.

I have FTX Global, Vector, Pilot’s Mesh 2018 and all good.

Hi Mwa05,

Did you notice any significant changes with the update. I saw there was an update released earlier this week but haven’t had a chance to read the change log. I believe the update brings it up to date with the P3Dv4 SDK so I’m guessing there’s a performance boost but did they add any eye candy like their WSSS.

The ZSPD old version lacked a bit on the nice eye candy details that we now see in their Singapore release.

thx

IM

Share this post


Link to post
11 minutes ago, Iceman2 said:

Hi Mwa05,

Did you notice any significant changes with the update. I saw there was an update released earlier this week but haven’t had a chance to read the change log. I believe the update brings it up to date with the P3Dv4 SDK so I’m guessing there’s a performance boost but did they add any eye candy like their WSSS.

The ZSPD old version lacked a bit on the nice eye candy details that we now see in their Singapore release.

thx

IM

I think it is on a par with WSSS to the extent I really like flying out of it, equally so with WSSS. I am in and out of both airports IRL so the fact I like them in P3D is testament to their robustness in the Sim.

Edited by mwa05

Share this post


Link to post

Might be then that the issue was related to my updated version. Might consider getting the full native P3Dv4 variant then, thanks for the heads up.

Share this post


Link to post
12 hours ago, exeodus said:

I have this scenery, as well as FTX Global and Vector, i do not recall any texture bleeding issues on my setup.

Thanks for the replies.

will take the plunge and purchase it hopefully I won’t have any issues 

Edited by mikeymike

Share this post


Link to post

Ok, I do not know what is different in my case, but based on the reports that there is no water bleeding through anymore, I took the plunge and got WSSS and ZSPD, and guess what? See for yourself:

2018-11-24_12-10-47-2dkf8z.jpg

2018-11-24_12-7-47-478yffq.jpg

That is really disappointing. I will now try to find this FTX Vector bgl to disable, but for WSSS, I have no idea what to do...

EDIT: I do not see anymore which FTX Vector file to be disabled, did someone edit the post?

Edited by AnkH

Share this post


Link to post

somebody please help with this I purchased zspd imagine sim and have the issue of the water body on right side of pic and north east of airport, vector/global installed

Share this post


Link to post
On 11/24/2018 at 6:18 AM, AnkH said:

Ok, I do not know what is different in my case, but based on the reports that there is no water bleeding through anymore, I took the plunge and got WSSS and ZSPD, and guess what? See for yourself:

2018-11-24_12-10-47-2dkf8z.jpg

2018-11-24_12-7-47-478yffq.jpg

That is really disappointing. I will now try to find this FTX Vector bgl to disable, but for WSSS, I have no idea what to do...

EDIT: I do not see anymore which FTX Vector file to be disabled, did someone edit the post?

Did you get yours resolved?

im still awaiting a reply from imaginesim and also here.

Share this post


Link to post

Regarding the issues with WSSS pictured above (I don't have that one just yet), it looks like the SODE jetways are displaced low, which suggests that perhaps there's an elevation correction file in the scenery that's not working.

I had this issue with their KLGA scenery--they had the elevation correction file in a folder named P3DSceneryWorldScenery under their KLGA LaGuardia P3Dv4 scenery folder, and an xml entry referencing it which did not work for me in P3Dv4.  I moved the scenery correction file located in that P3DSceneryWorldScenery folder to the scenery\world\scenery subfolder in my P3D v4 folder, and removed the Addon.Component section that contained the elevation correction from their add-on.xml file, and that fixed the elevation problems, including missing runway lights, jetways sunk below ground level, shimmering water plateaus etc.

I'm only guessing, but it might be there's a simiilar issue with the same sort of implementation of an elevation correction in WSSS causing your bleed through and too-low jetway heights.

Regards

 

Share this post


Link to post
2 hours ago, w6kd said:

Regarding the issues with WSSS pictured above (I don't have that one just yet), it looks like the SODE jetways are displaced low, which suggests that perhaps there's an elevation correction file in the scenery that's not working.

I had this issue with their KLGA scenery--they had the elevation correction file in a folder named P3DSceneryWorldScenery under their KLGA LaGuardia P3Dv4 scenery folder, and an xml entry referencing it which did not work for me in P3Dv4.  I moved the scenery correction file located in that P3DSceneryWorldScenery folder to the scenery\world\scenery subfolder in my P3D v4 folder, and removed the Addon.Component section that contained the elevation correction from their add-on.xml file, and that fixed the elevation problems, including missing runway lights, jetways sunk below ground level, shimmering water plateaus etc.

I'm only guessing, but it might be there's a simiilar issue with the same sort of implementation of an elevation correction in WSSS causing your bleed through and too-low jetway heights.

Regards

 

Hi 

would this be the same issue with zspd??

 

thanks 

mike

Share this post


Link to post
1 hour ago, mikeymike said:

would this be the same issue with zspd??

I don't think so.  There is a P3DSceneryWorldScenery subfolder in the ZSPD folder, but the only file in there looks to be a landclass bgl by its name and by where it's installed via the xml definition structure.

I'd look to an errant elevation correction in your Vector installation as the most likely cause, but also make sure you don't have an elevation file from another addon in scenery\world\scenery.  AFAIK, the previous version of ZSPD did not use an elevation file, either.

Third-party mesh could also be behind this, especially if you've set a mesh resolution that's higher than the source data, which can cause aberrant interpolations to distort the topography enough to poke through the ground flatten.  Try reducing your mesh resolution a couple notches if you're running 3rd party mesh.

Regards

Share this post


Link to post
14 minutes ago, w6kd said:

I don't think so.  There is a P3DSceneryWorldScenery subfolder in the ZSPD folder, but the only file in there looks to be a landclass bgl by its name and by where it's installed via the xml definition structure.

I'd look to an errant elevation correction in your Vector installation as the most likely cause, but also make sure you don't have an elevation file from another addon in scenery\world\scenery.  AFAIK, the previous version of ZSPD did not use an elevation file, either.

Third-party mesh could also be behind this, especially if you've set a mesh resolution that's higher than the source data, which can cause aberrant interpolations to distort the topography enough to poke through the ground flatten.  Try reducing your mesh resolution a couple notches if you're running 3rd party mesh.

Regards

Thanks for the feedback

i do have freemesh x installed 

will try reinstalling vector also 

I believe 1.6 is available 

and also check the world scenery folder.

will report later.

thanks again.

mike

Share this post


Link to post
5 hours ago, w6kd said:

I don't think so.  There is a P3DSceneryWorldScenery subfolder in the ZSPD folder, but the only file in there looks to be a landclass bgl by its name and by where it's installed via the xml definition structure.

I'd look to an errant elevation correction in your Vector installation as the most likely cause, but also make sure you don't have an elevation file from another addon in scenery\world\scenery.  AFAIK, the previous version of ZSPD did not use an elevation file, either.

Third-party mesh could also be behind this, especially if you've set a mesh resolution that's higher than the source data, which can cause aberrant interpolations to distort the topography enough to poke through the ground flatten.  Try reducing your mesh resolution a couple notches if you're running 3rd party mesh.

Regards

Thanks for the feedback

i do have freemesh x installed 

will try reinstalling vector also 

I believe 1.6 is available 

and also check the world scenery folder.

will report later.

thanks again.

mike

Share this post


Link to post

I have all of the above to no avail.

have no idea what’s going o.

rediculous

pay for a product and then try to figure out how to fix it.

wow 

Share this post


Link to post

Perhaps. Layer Bgl to switch for now?

until fixed?

regards

mike

Share this post


Link to post
14 hours ago, w6kd said:

Regarding the issues with WSSS pictured above (I don't have that one just yet), it looks like the SODE jetways are displaced low, which suggests that perhaps there's an elevation correction file in the scenery that's not working.

Might be, but no. I checked the SODE jetways, they are correct (you can see it on the pictures, the wheels of the SODE jetways are correctly on ground), nothing wrong there.

The problem: if it IS related to my VECTOR installation, I have no idea how to solve it. As the vector data covering those regions is usually about 20x20km, simply disabling it would help nothing but lead to errors around the airport.

I will check the mesh setting, as I use Pilots Global Mesh. But: why should I have to adjust something I never needed to adjust before? No other scenery shows this issue. Honestly, this makes me really angry, I had exactly the same issue back in the FSX days and discussed it for hours with the Imaginesim support and now, again the same bulls*. I really do not know why Imaginesim is obviously not capable of getting this right...

Share this post


Link to post

Ok, I got a message from Imaginesim: I should reduce the water detail from "ultra" to "high". I will certainly try this, however this cannot be the final solution, that's simply ridiculous. I just checked my mailbox, I had exactly the same discussion with the Imaginesim support back in August 2016. So obviously, they were not capable to resolve this bug in their current release, what a bummer...

Share this post


Link to post
3 hours ago, AnkH said:

Ok, I got a message from Imaginesim: I should reduce the water detail from "ultra" to "high". I will certainly try this, however this cannot be the final solution, that's simply ridiculous. I just checked my mailbox, I had exactly the same discussion with the Imaginesim support back in August 2016. So obviously, they were not capable to resolve this bug in their current release, what a bummer...

I’m still waiting on a response from them.

about zspd, I have tried all the above I have mentioned to try fixing it.

i am considering getting a refund. 

So upset about this.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now