Try
http://192.168.0.1:5500/gui/
Replace the 1 (one) with your computers ip #
clrCoda wrote in Mon Jun 08, 2015 8:17 pm:it's 5500 on you machine because that is what you have it set to.
clrCoda wrote in Mon Jun 08, 2015 8:17 pm:There is no error. Just no connection in the last two daily builds, but no problem at all, as I keep re-iterating, in the build from last week.
clrCoda wrote in Mon Jun 08, 2015 8:17 pm:So long as the port is set correctly and matched to the browser, there should be no difference if I use the original 8080 port, or what ever personal port I set
Thanks for trying but you are not answering the problem.
Ray
wkitty42 wrote in Tue Jun 09, 2015 3:54 am:clrCoda wrote in Mon Jun 08, 2015 8:17 pm:it's 5500 on you machine because that is what you have it set to.
no... it is 5500 on my machine because it didn't set it to anything and that's what FgRUN told me it was way back when... since then i've never tried to argue the point... i've just stated it how it has been...
Torsten wrote in Wed Feb 25, 2015 11:06 pm:
All this is already in GIT. If you run the latest development code and want to try hands-on, start FlightGear with the internal web server enabled (--httpd=8080) and point your browser at http://<your-flightgear-computer>:8080/gui/ or http://localhost:8080/gui/ if you are on a single computer.
You need a descent browser for this. Latest Firefox, Chrome and Safari should work. Operating systems tested are Linux, OSX 10.9 and 10.10, iOS (latest) and Android (latest). It doesn't scale down to small displays yet. 7" and less is a mess.
Technologie behind is HTML5, CSS3, JavaScript and some excellent JavaScript libraries. Mainly jquery, jquery-ui, knockout, require, leaflet and flotcharts.
Hope you like it.
Torsten
wkitty42 wrote in Tue Jun 09, 2015 3:54 am:clrCoda wrote in Mon Jun 08, 2015 8:17 pm:There is no error. Just no connection in the last two daily builds, but no problem at all, as I keep re-iterating, in the build from last week.
and you are are not seeing any errors on the server side??clrCoda wrote in Mon Jun 08, 2015 8:17 pm:So long as the port is set correctly and matched to the browser, there should be no difference if I use the original 8080 port, or what ever personal port I set
Thanks for trying but you are not answering the problem.
Ray
well, duh! and you're welcome... sorry for even trying to help... that won't happen in the future, though... while i may be a JANG, it doesn't mean that i don't have some support knowledge and information that may help you... oh well... your loss... in the mean time, don't shoot the messengers... it may be that some JANG has the answer to your problems... especially since a lot of the base fgfs stuff is changing from what ""you guys"" are used to...
Users browsing this forum: No registered users and 8 guests