WIP Little Navmap (like FsNav for FS2004 and freeware)

Ok, a rundown of what works now and why:

No airports, navaids, airways, etc showing on the map. . .that would be because I was in FSX and in the Scenery Library dropdown. . .Prepar3D was selected. Upon loading it seems to want to default to P3D.

Aircraft not showing with NavConnect running and connected (supposedly). . .it was not connected but attempting to connect, the reason it wouldn't is because the ISP I copied over was off by one digit

CTD after about 10 minutes of flying. . .No idea why that happened (twice) possibly due to something going on in NavConnect timing out because the ISP was incorrect. Who knows.

Interestingly when I made a flight plan, I made one with four airports. . .starting with South Jersey Regional, each successive airport was placed above the departure airport rather than below which meant that when I placed the destination airport I had a reverse flight plan that wanted to start at Trenton/Mercer (which was actually the destination) and land at SJR (which was the departure). I'll work on that one. . .probably something I didn't do correctly.

Finally, I seem to be getting a fairly significant FPS/Stuttering hit while running the program. I'll have to do more investigating to see if there's any way to reduce that because as it is right now it's a major problem while flying.
 
Adonis said:
What I'd like to see added is a possibility to show the Project Tupolev, SCS and SamDim plane RSBN beacons from the two used types of databases.
Click to expand...
No idea what data format they use, but I think this could be solved by adding custom waypoints functionality with CSV import/export in a future release.

falcon409 said:
Ok, a rundown of what works now and why:

No airports, navaids, airways, etc showing on the map. . .that would be because I was in FSX and in the Scenery Library dropdown. . .Prepar3D was selected. Upon loading it seems to want to default to P3D.

Aircraft not showing with NavConnect running and connected (supposedly). . .it was not connected but attempting to connect, the reason it wouldn't is because the ISP I copied over was off by one digit

CTD after about 10 minutes of flying. . .No idea why that happened (twice) possibly due to something going on in NavConnect timing out because the ISP was incorrect. Who knows.

Interestingly when I made a flight plan, I made one with four airports. . .starting with South Jersey Regional, each successive airport was placed above the departure airport rather than below which meant that when I placed the destination airport I had a reverse flight plan that wanted to start at Trenton/Mercer (which was actually the destination) and land at SJR (which was the departure). I'll work on that one. . .probably something I didn't do correctly.

Finally, I seem to be getting a fairly significant FPS/Stuttering hit while running the program. I'll have to do more investigating to see if there's any way to reduce that because as it is right now it's a major problem while flying.
Click to expand...

The simulator in the Scenery loading dialog is not synchronized with the simulator selection in the menu. I think this can be confusing because sometimes you don't reload what you see.
The program keeps separate scenery databases for each simulator and you can switch between them on the fly.
If one of them is not loaded you won't see anything when switching to the wrong one. I will synchronize the dialog and the map in the future.

About the CTD: I (rarely) had some in the past that were caused by the background updates in the "Flight Plan Elevation Profile" dock window. Close that window, that will end all background updates for elevation data which also might save some FPS. Maybe that helps.
A wrong IP address should not cause any crash, only an error message. Although the error message can show up to a minute later in some cases.
When running all on the same computer simply use "localhost" to connect.

About flight plan building: The logic depends on the menu item you used to add an airport:
If you use "Set as Departure/Destination" the new airport always *replaces* the current departure or destination
If you use "Add to flight plan", the airport (or waypoint) is added to the nearest route leg or waypoint. So this might be added before the departure or it can be appended to the route after the destination.
The drag and drop editing mode on the map is explained in the manual here.

About stutters: I'm running all on my old and trusty Core i7 975 at 4 GHz, FPS externally locked to 60 (with low settings in FSX) and only get the usual FSX stutters from time to time.
I'm quite sure the stutters are an affinity mask/priority problem. I'll post my settings when I'm at my flying computer.
You can also try to decrease the update interval in Navonnect.

Alex
 
albar965 said:
Hi All,

I'm the author of this little thing.

Some remarks about questions in this thread:

Yes, it can build flight plans (PLN files, XML format) for FSX, FSXSE, P3D. No other formats supported yet. I'm open for proposals.

The manual is available online as one single HTML page. So printing or converting to PDF should be no problem. It also comes with the program but the online version has some more updates and clarifications.

About features compared to Plan-G:
Plan-G has much more functionality than Little Navmap (Vatsim stuff, airspace boundaries, approaches, traffic, multiplayer aircraft display, user waypoints, etc.).
I used it a lot in the past but had too many problems with freezes as well as lacking airport information (e.g. cannot find out if an airport has lighted runways).


About the development:
There was already a bunch of beta releases, that fixed a lot of problems reading scenery, thanks to a very helpful community.
I think it is getting quite stable now and I will create a final release soon which will not differ much in functionality (but more in number of bugs :mixed-smiley-010:) compared to the beta releases.

The next goal is a release version 1.2 that will have a lot of small improvements. Here is list of tickets that I assigned for this version.

falcon409: I answered you post at fsdeveloper.

Alex
Click to expand...


Many thanks for all your hard work Alex, and welcome to the forum.


Regards,
Ian
 
Hi Ian,

thank you for the welcome.

I'm still digging through the code fixing bugs, testing stuff and hope to have that stable release finished soon.
Then I'm looking forward to add new functionality.:smile-new:

Alex
 
Hi All,

Little Navmap stable version 1.0.5 released

A big thank-you to all the people supporting me throughout the beta phase, sending me their log files, screen shots, friendly messages and more.

There is no new functionality compared to the last beta version. New features will be added in the next development cycle.

Fixed since the last beta 1.0.4:

  • Scenery reading errors for airports without city name.
  • Errors reading scenery.cfg file.
  • Exclude options did not work for some scenery paths.
  • Wrong order of flight plan when adding waypoints.
  • Overview overlay loosing background image.
  • Valid start position in flight plan not recognized.
  • Display of narrow and closed taxiways.
Improved:

  • Disabling aircraft tracking on double click and other actions.
  • Simulator selection in loading dialog now synchronized with map.
  • Smoothed user aircraft movement a bit.
  • Added help button to various dialogs.
  • Many additions and clarifications in the manual.
Download LittleNavmap-win-1.0.5.zip for Windows
Download LittleNavmap-macOS-1.0.5.dmg for Apple macOS

Little Navconnect stable version 1.0.1 was released too

Download LittleNavconnect-1.0.1.zip



Alex
 
You must log in or register to reply here.
Back
Top