By Chris Kirkman 1396980
#518580 1. The aircraft identifiers, when seeing other traffic, are so small they're basically unreadable. I'll attach a screenshot.
2. As a developer, I can see several areas for improvement; however, it appears this application is no longer being updated. Any word on further development or another client being developed?
3. Message screen color scheme is very difficult to read. Any way to change text color, or background opacity on message screen? See attached screenshot as well.
4. Liveries of other aircraft. How is this defined? I've had this plug-in installed since early this year, so don't remember how/where the liveries come from. I consistently run into "Jet Blue" and "United" or "US Air"; however without the liveries all I see is "JAS". Very annoying as well.

ImageRotate-MD-80-XP11_42 by Chris Kirkman, on Flickr

ImageRotate-MD-80-XP11_43 by Chris Kirkman, on Flickr

Image2017-10-15 13_21_30-X-System by Chris Kirkman, on Flickr
By Mathew Sutcliffe 1154576
#518608 1. This is a known problem when using high levels of anti-aliasing with HDR. No solution as yet, but disabling those settings may help.
2. It is still being maintained, but active development depends on Chris Collins having the time to work on it. The current version was released 4 months ago. And there is swift which is still a work in progress.

4. XSquawkBox uses CSL models installed in X-Plane/Resources/plugins/XSquawkBox/Resources/CSL. Bluebell CSL package is the most up-to-date.
By Christopher Collins 1304731
#518796
Chris Kirkman 1396980 wrote:1. The aircraft identifiers, when seeing other traffic, are so small they're basically unreadable. I'll attach a screenshot.
2. As a developer, I can see several areas for improvement; however, it appears this application is no longer being updated. Any word on further development or another client being developed?
3. Message screen color scheme is very difficult to read. Any way to change text color, or background opacity on message screen? See attached screenshot as well.
4. Liveries of other aircraft. How is this defined? I've had this plug-in installed since early this year, so don't remember how/where the liveries come from. I consistently run into "Jet Blue" and "United" or "US Air"; however without the liveries all I see is "JAS". Very annoying as well.


Nice to see my efforts are not appreciated at all by some.

1) Turn off MSAA. As you claim to be a developer, you can fix this yourself and submit the patch to me. (See https://github.com/kuroneko/libxplanemp/issues/16). The lack of a test plugin for libxplanemp is also a significant cause of slowdown on this one, and is necessary to fix a major bug I'm currently tearing my hair out over when I have time to work on x-plane stuff (being the Async OBJ8 loading bug - (https://github.com/kuroneko/libxplanemp/issues/15).

2) There is further development, when I have time, and only when I have time. I do not offer comprehensive roadmaps because people read too much into them. Features get added when they get added. To give you some idea as to scale of the work planned, I currently have 19 outstanding improvement/bugfix items remaining in my todo list. Between about 1.3.2 and 1.3.3, I cleared off 11 items. (hard to know because I can't remember precisely when I started the todo list).

3) No. I'll have to dig around a bit to work out where the colours come from but I'm pretty sure they're hardcoded in XSB itself - I can probably add twiddles to the config for the next release, and sort out UI later. I have added a todo item to that effect.

4) This is a complicated subject in full, but it sounds like what you really want to know is how to read the manual. Read the manual - Page 4 - "Installing Additional Model Sets". The best model set (CSL) to install right now is the Bluebell OBJ8 CSL. If you prefer breadth of support over quality, you want X-CSL. Just bear in mind that X-CSL models will cease working in the future.
By Brett Holcomb 1053345
#522376 I am glad to see that you are looking at fixing the color and text issues at some point. For me it's unreadable due to the colors and size. The ideal would be to make it a window that we can drag off to another screen and resize (as well as change colors) like the map in XPlane 11.

Thanks for XSB.
By Christopher Collins 1304731
#522463
Brett Holcomb 1053345 wrote:I am glad to see that you are looking at fixing the color and text issues at some point. For me it's unreadable due to the colors and size. The ideal would be to make it a window that we can drag off to another screen and resize (as well as change colors) like the map in XPlane 11.


You are literally late to the party.

I've started rewriting the UI code to make it compatible with the XP11 windowing system and with VR positioned windows (presently it is not compatible with either).

The new UI code /might/ make it into 1.4 too since it's actually easier to support in XP10 than it is in XP11 (I spent a day tearing my hair out over how to correctly implement the coordinate space remapping and glScissor support to make the UI library work because of how XP11 fidgets with the coordinate space depending on if a XP window is "docked" or not).

Try not to read anything into the WIP screenshot options visible - a lot of those will be going away as the 2.0 client gets refined and the obsolete features get removed. Nothing is (even close to) final yet.

WIP screenshot:
Image

Obligitory Blooper:
Image