Jump to content

Nassau Issues


ChinNoobonic

Recommended Posts

  • Replies 161
  • Created
  • Last Reply

Personaly, i still have no glasshield on terminals like someone else has also reported.

The update did not change that.

By the by, is it the same developer who has developed MYNN and KASE ?

Dom

 

Link to comment
Share on other sites

6 hours ago, mason-dom said:

Personaly, i still have no glasshield on terminals like someone else has also reported.

The update did not change that.

By the by, is it the same developer who has developed MYNN and KASE ?

Dom

 

No glass sounds like a SODE issue.  It seems the glass is added through SODE for some reason.

 

Joe L.

Link to comment
Share on other sites

The glass is added via SODE for a good reason.

If it's not showing up you have some issues with SODE and not our scenery. Not much we can help there.

Link to comment
Share on other sites

Sode , it  is not required if you want to let it look as a default airport.

 

so Yes  you need it if you need a full working airport.

 

Don't ask me if I am happy with Sode , but that is another thing, I think there must come a worldwide

guideline to developers how to use things like Apcontroller , Sode, objectflow etc. to create a standard

that don't drive us users sometimes crazy how to restore things back to normal.

as flightsimmer you also have to be an IT specialist to keep your plane flying.

 

Link to comment
Share on other sites

13 hours ago, sydney1962 said:

Sode , it  is not required if you want to let it look as a default airport.

 

as flightsimmer you also have to be an IT specialist to keep your plane flying.

 

Okay, I'll do without Sode.

 

So much frigging truth in that last statement.

Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...

Hey guys,

as already stated a month ago.. we're still looking into issues and ways to optimize stuff in Nassau.

We're currently implementing new techniques allowing better looks and performance on Newcastle Airport. If those techniques will run as they're supposed to and deliver the performance and quality we want we'll implement them in Nassau.

Ray: If you send us your E-Mail via the Aerosoft Forum or Facebook you're more then welcome to join testing for Newcastle and report performance on your end.

That's all for now guys

Ps. We've attached two images showing the current state of Newcastle. Remember, it's a W.I.P

Please login to display this image.

Please login to display this image.

Link to comment
Share on other sites

  • 2 weeks later...

I just downloaded the installer...the download page says it's version 1.01, but the installer says it's V1.00 and the product.cfg file says version=0100

 

So...where's the updated version?

 

Regards

 

Bob Scott

Link to comment
Share on other sites

Hello,

I am having the same issue as Bob (w6kd) after reading this thread and checking my ver. I see where I had reinstall (June 2 of this year) it but it still says ver 1.00.

Also I can't get use of the Heavy gates as GSX says they are all too small for my B772.

I am re-downloading the scenery in hope that this is corrected.

However if I am doing or not checking something, your help will be appreciated.

Regards,

Kenny

 

P.S Just to updated that after downloading and reinstalling the product.cfg is now showing version-0101, unfortunately the issues remain. SODE gates not working and ADE cant edit for some reason.

Link to comment
Share on other sites

  • 3 weeks later...

Gentleman,

just a quick update:

We've successfully implemented new techniques on two upcoming scenerys. Those techniques will be used on the Nassau files as soon as those two projects are out. 
Expect a performance boost :)

 

Link to comment
Share on other sites

Hello IDS Studios,

 

Also please keep in mind that the AFCAD has some issue with GSX. The heavy gates are too small for the B772 (PMDG) and SODE is a hit or miss at most time. By that, the Gates don't work with the GSX menu and when you try it via the SODE menu, you get No trigger objects found.

 

Regards,

Link to comment
Share on other sites

  • 1 month later...

Sorry to kick the dust off this thread, But I had an OOM today @ MYNN, and this is a very rare occurrence for me.

Had anything been discussed about the missing files  MYNN_RAMP_LIGHTS.dds, MYNN_SHADOWSA.dds and MAT.2_COLOR.dds ?

As quite clearly I have something missing.

Also, Has no one ever commented on texture files size with this addon? There's a single file that 64.0 MB !!!!! Some 21 and Some 10MB , After checking my EDDF V2.0 there are none even remotely close to that size. this seems to be something that should be addressed no?

I've also noticed that while I've downloaded the update 1.01, It is still version 1.00. Could someone look into that.

Thanks! 

Please login to display this image.

Link to comment
Share on other sites

the sheer of single textures is not always a sign of a problem. If you use one big texture for large area (with LOD in the texture) it may be more efficient than using many smaller ones. The problem is more in the resolution of the texture (a 4096x4096 texture of 2MB may have a worse impact than a 16MB texture of 1024x1024)

 

It's the way the textures are handled (or "can be handled") in the scenery or airplane. (well... it looks there may be some room for improvement here B))

 

What tells you that the files "MYNN_RAMP_LIGHTS.dds, MYNN_SHADOWSA.dds and MAT.2_COLOR.dds" are missing ?

Link to comment
Share on other sites

Aerosoft...it has been over two MONTHS since I submitted a ticket and posted here inquiring as to why the MYNN installer, labelled V1.01 in the filename, still comes up as V1.00 when the installer is run.  Your support folks told me they were checking with the dev, and the trail went cold from there.  Your lack of follow-up on this has me extremely frustrated.

 

There is a problem in P3D with SODE jetways having the head of the jetway cocked to the full counterclockwise position, which is supposed to have been fixed in the current version of SODE with V1.3+ compliant jetways, and IDS lists SODE 1.3.2 compliant jetways as one of the fixes they included in V1.01.  The jetways are still a problem using a freshly downloaded copy of the scenery, and the installer still displays "V1.00" when run, which suggests that you still have not gotten the installer updated correctly several months after this was brought to your attention.

 

Given that it has been several months already, could we please get some expedited action on an updated installer that includes the current version 1.01 files?  Please??

 

Regards

 

Bob Scott

Link to comment
Share on other sites

7 hours ago, data63 said:

What tells you that the files "MYNN_RAMP_LIGHTS.dds, MYNN_SHADOWSA.dds and MAT.2_COLOR.dds" are missing ?

ShowMissingTextureAlert=1 activated in the scenery section of the FSX.cfg file will pop up and error on loading MYNN.

Link to comment
Share on other sites

the MissingTextureAlert was introduced as a debugging feature. The messaged are mostly a "false positive" as developers often use some textures in development and testing which are not used in the final build but are forgotten to be deleted in the refences (happens more often than you might think).

 

As long as you don't have problems with missing textures or you are looking for missing textures a reason for CTD (sometimes occuring with AI traffic) it's no real problem and the MissingTextureAlert should be turned off

Link to comment
Share on other sites

On 10/17/2016 at 10:35 AM, data63 said:

the MissingTextureAlert was introduced as a debugging feature. The messaged are mostly a "false positive" as developers often use some textures in development and testing which are not used in the final build but are forgotten to be deleted in the refences (happens more often than you might think).

 

As long as you don't have problems with missing textures or you are looking for missing textures a reason for CTD (sometimes occuring with AI traffic) it's no real problem and the MissingTextureAlert should be turned off

Yes, I'm fully aware of the design of the missing texture flag, but as you can see from my post above, there is something missing from my install. 

Definitely not my first rodeo! 

Link to comment
Share on other sites

I just checked the dates on the files in my scenery directory after re-downloading and re-installing "V1.01" of this scenery.  They are all dated 20 Nov 2015--IDS says V1.01 was released on 2 Jun 2016, so it appears that the installer, despite being labelled V1.01, does not, repeat does not contain any of the updated V1.01 files.

 

The Product.cfg file in the directory still says Version=0100, even after using the current "V1.01" installer, and when I ran the installer I downloaded yesterday, in the upper right corner of the window of the installer program it says V1.00

 

Can...we...please...get...the...updated..scenery...PLEASE???

 

Regards

 

Bob Scott

Link to comment
Share on other sites

I just downloaded the file (AS_NASSAU-BAHAMAS_FSX-P3D-FSXSTEAM.ZIP) from the "other region" server instead of the "USA Mirror". 

 

Although both the file size and name of the downloaded .zip file was the same as what I got from the USA mirror, the installer .exe embedded inside the zip on the "other region" server was both larger (539,071K vs 515,009K) and newer (2 Jun 2016 vs 25 Nov 2015). 

 

That file on the "other region" server is indeed the actual V1.01 installer.  I checked, and the one on the German server is also the correct file.  As of right now, the one on the USA mirror server is NOT. 

 

Additionally, the IDS_MYNN.xml file that is installed in the SODE xml directory by the V1.01 installer has blank lines in it which causes attempts to operate the SODE jetways to fail.

 

It sure would have been nice to have some meaningful assistance from Aerosoft sorting this mess out over the course of the last 10 weeks...

 

Bob Scott

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

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. Privacy Policy & Terms of Use