Facebook

Login

Lost password?

Support Sailonline

If you haven't already - join the SAILONLINE YACHT CLUB!

Please also consider making a donation - all amounts are greatly appreciated!

Profile for A2



Name A2
Email Address n/a
AvatarUsers avatar
Posts347
Board Signature
To Boldly go where no router has gone before . . . . . or since.
  • Re: Optimum Angles
    Board » Technical Support
    * Technical Support has been moved to the Dead Letter Office *
    To Boldly go where no router has gone before . . . . . or since.
  • Re: Optimum Angles
    Board » Technical Support
    Well obviously my clumsy attempts to find useful information from the Adobe forums for this problem has not been successful, which raises the question why the cognoscenti has not done so directly. However I am at odds with the assumption that this is a User only circumstance. My suspicions are that Adobe may be arbitrarily curtailing access to Flash versions which they deem to be out of date even though no such limitation exists within the client itself.

    The Classic client works because it does not access files from Adobe. What is needed from my point of view is a stand alone SWF version that does not require the SWZ precursor to test this hypothesis.

    This might explain why only users with computers of a certain age are affected as long as they have not actually had to clear their caches of versions that are still functional before returning to Adobe for a reload.
    To Boldly go where no router has gone before . . . . . or since.
  • Re: Optimum Angles
    Board » Technical Support
    I am not aware of any information being volunteered here by Sailonline NavSim AB relating to whether any files under their control has changed recently concurrent with the various difficulties under discussion in this thread nor to what extent if any they are able or willing to implement remedies as needed.

    Adobe may be at the root cause of this perplexing dilemma as there are similarities found in their Forum https://forums.adobe.com/thread/723549 here.

    Although being able to decipher such geeky stuff is above my pay grade.

    Implied from what I can tell is that Adobe may have changed certain files without notice or some files may have an inherent expiration which is now out of date.

    For Example here is one excerpt that caught my eye:

    "two solutions, depending on how important are external libraries for your app(s), neither of which involves changing a single line of code.
    1. Disable framework RSLs and deploy a "fat" app
    2. Disable digest authentication for RSLs, and deploy the compiled framework SWFs along with your app. In this case, the old SWZ files are not interesting anymore, and you must deploy all the generated files, including the "framework.swf" etc."

    Even if this proves not to be relevant in fixing the problem here I believe that it does emphasize the prudence of keeping all components involved in stasis locally and not at the whim of Adobe's future inclinations.

    Anyone that is having this problem also please post your Operating System flavors & such so that it is possible to discern any pattern that may or may not exist from the User side.

    --- Last Edited by A2 at 2015-07-26 01:39:56 ---
    To Boldly go where no router has gone before . . . . . or since.
  • Re: Optimum Angles
    Board » Technical Support
    The problem remains the same after several weeks.

    --- Last Edited by A2 at 2015-07-26 01:41:25 ---
    To Boldly go where no router has gone before . . . . . or since.
  • Re: Optimum Angles
    Board » Technical Support
    avoid loading adobe.com's crossdomain.xml by hosting the swz files on your own server. Just copy the swz files to the same directory as your application and modify the RSL URLs.

    The RSL URLs are modified by removing the URL pointing to the adobe hosted site and keeping the "framework_4.5.0.20967.swz" URL.
    To Boldly go where no router has gone before . . . . . or since.
  • Re: Optimum Angles
    Board » Technical Support
    I punched up the Classic Client & it does load correctly. I noticed that the Framework XXX.swz file loads directly from Sailonline.org and when it is complete the XXX.swf follows.

    This is what is Not happening for the Beta Client.

    SWZ does not begat SWF
    To Boldly go where no router has gone before . . . . . or since.
  • Re: Optimum Angles
    Board » Technical Support
    Yes it returns

    [RSL 1 of 3]

    error #2046
    To Boldly go where no router has gone before . . . . . or since.
  • Re: Optimum Angles
    Board » Technical Support
    # 2032 [Stream Error]

    This error indicates that the SWZ or SWF file is not being found.

    The frequently occurs if the client is not able to download the signed framework RSL (Runtime Shared Library) from the Adobe web site, and you have not deployed a local signed framework RSL. If the client has limited or not internet connectivity, be sure to deploy the local framework RSL to a location that is accessible to the client. For more information, see Using the framework RSLs.

    It can also occur if Flash Player tries to load a custom RSL that is not available. For example, if you specified only “mylib.swf” as the value of the rsl-url parameter to the runtime-shared-library-path option, but the SWF file is actually in a sub-directory such as /rsls, then you must either recompile your application and update the value of the rsl-url parameter to “rsls/mylib.swf”, or move mylib.swf to the same directory as the application’s SWF file.
    ---------------------------
    # 2046

    This error indicates that the loaded RSL was not signed properly. In the case of framework RSLs, the framework’s SWZ file that the application attempted to load at run time was not a properly signed SWZ file. You must ensure that you deploy an Adobe-signed RSL, or be sure to use the signed framework RSLs that are deployed on the Adobe web site.
    ---------------------------
    # 2048

    The cause of this error is that you do not have a crossdomain.xml file on the server that is returning the RSL. You should add a file to that server. For more information, see Using cross-domain policy files.

    If you are loading signed framework RSLs from the Adobe web site, you should not get this error.

    If you put the crossdomain.xml file at the server’s root, you do not have to recompile your application. This is because the application will look for that file at the server’s root by default, so there is no need to explicitly define its location.

    If you cannot store a crossdomain.xml file at the remote server’s root, but can put it in another location on that server, you must specify the file’s location when you compile the application. On the command line, you do this by setting the value of the policy-file-url argument of the runtime-shared-library-path option.

    In the following example, the RSL SWF file is located in the /rsls directory on www.domain.com. The crossdomain.xml file is located in the same directory, which is not the server’s root, so it must therefore be explicitly specified:

    mxmlc
    -runtime-shared-library-path=
    ../lib/mylib.swc,
    http://www.mydomain.com/rsls/myrsl.swf,
    http://www.mydomain.com/rsls/crossdomain.xml
    Main.mxml
    ---------------------------
    Requested Resource Not Found

    You might find this error in your web server logs. If you deploy the RSL SWF file to a location other than that specified when you compiled the application, then you will get an error similar to this when the application tries to run.

    The solution is to either recompile your application and correct the deployment location of the RSL SWF file or to move the RSL SWF file to the location that the application expects.
    To Boldly go where no router has gone before . . . . . or since.
  • Re: Optimum Angles
    Board » Technical Support
    Perhaps a different approach to this problem in order. The Race (beta) Client has worked well for over 3 years on my machine. For whatever reason it does not assemble correctly for me anymore. I do not know if all these necessary components come from SOL itself or some of it is from a 3rd party.

    Would it be possible to package All of it together so that it could reside on my hard drive & only need to task SOL for the individual races plus the weather as needed ?
    To Boldly go where no router has gone before . . . . . or since.
  • Re: Optimum Angles
    Board » Technical Support
    Here is the HTTP Archive (HAR) file it created for windy/run/848
    To Boldly go where no router has gone before . . . . . or since.

Races

Next Race: 00d 00h 00m


Current Races:

SSANZ Safety at Sea Two-Handed Triple Series 2015 - Race 3
Welcome to the third and final race of this year's SSANZ Triple Series on the waters off Auckland, New Zealand. This is the Baltic 50, and again Sailonline will be racing against members of the Young 88 Association!
Race #863
Chart from brainaid.de
Young 88 POLAR
WX Updates: 0430 / 1030 / 1630 / 2230
Ranking: SSANZ 2015 -SYC
ALT. CLIENT Classic
Race starts: Sep 04th 21:10 Registration Open!
GO TO RACE

The Vineyard Race 2015
The Stamford Yacht Club welcomes Sailonline to its 2015 running of The Vineyard Race. The course runs from Stamford to Buzzard's Bay Light near Martha's Vineyard Island and back again, leaving Block Island to starboard. Sail against the real fleet in your Santa Cruz 52.
Race #860
NORfrom brainaid.de
Santa Cruz 52 POLAR
WX Updates: 0430 / 1030 / 1630 / 2230
Ranking: SYC - SYQ3 -SYCCH - SUPSOL
ALT. CLIENT:Classic
Race starts: Sep 04th 17:00 Registration Open!
GO TO RACE

Go to race archive

SYC Ranking

  1. Sailonline Yacht Club Member rumskib
  2. Sailonline Yacht Club Member kenza
  3. Sailonline Yacht Club Member rafa
  4. Sailonline Yacht Club Member bonknhoot
  5. Sailonline Yacht Club Member Dingo
  6. Sailonline Yacht Club Member MustangMark
  7. Sailonline Yacht Club Member StIngFI
  8. Sailonline Yacht Club Member Neuroman
  9. Sailonline Yacht Club Member Franci
  10. Sailonline Yacht Club Member SimeMali

View full list

Series

Mobile Client

SYC members have the benefit of access to our mobile/lightweight web client!

The mobile client