wim1976

function OnDraw_Gauges() w,h = gfx.getScreenSize() gfx.setColor(1,0,0,1) gfx.drawString("hello world", w/2, h/2 )endOK, this is a very old thread, but why doesn't this code work anymore in Gizmo. I have troubles getting the gfx. functions to work

Excellent innovation. And could the 2D panels als be activated with keys or buttons?

What has Prosim to do with GoFlight. I don't see the point.

I found a big hint for my question. In the console the undefined events are logged when 'trapping' these events, resulting in a log: undefined function... With this info I can start programming an event procedure. But are these events somewhere documented? So I can understand the 'why' somewhat better.

I have take a look at the console code. Nice stuff, but where can I find more info about events. Which events can occur for the different gui (and other) elements?

Thanks, that's helpful!

I am learning Gizmo with baby-steps. To do this I started making a checklist using checkboxes and lables etc. from the gui lib. But how can I check if a window is already open. I want to prevent that a window is opened twice, how can I do this? Until now I have tried to find an event for the window (e.g. AfterClosed) or to check the window state. But with no succes.

If found the problem. The top part of the code was not out-commented, so the module were not recognized by IntelliJ. Commenting the first rules was the solution for the problem. Maybe the code on Github can be updated.

Thanks, added to IntelliJ. Is see some form of auto-completion, but it doesn't work good. When I type A function e.g font.drawstring() no autocompletion is shown. When I type drawstring then I see the function. In your screenhots on Github I saw you have also a library G64 (besides the G63 with autocompletion stubs). Is this library also needed and where can I find this one. I have tried Gizmo-firmware from Github but with no result.

Ben, The link in your post of 2014/1/3 doesn't work anymore.

For me X-Aviation sells quality products, but at X-Plane.org you have to look carefully or you will end up buying some crap.

Flown form RJBB (Kansai Intl) to RJTT (Tokyo Haneda Intl), with a great view on mount Fuji. Of course with the HD Mesh of AlpilotX.

After a quick test, using the fps_test parameters I found that the performance for CPU-bound situations improved a lot (with results I have never seen before!). I hope that Laminar Research will optimise the GPU-code also, so we can see a performance gain on the heavy settings also. My test-system - CPU: I3570K (4,5 GHz) - GPU: Gigabyte GTX 770 (4GB) - Mem: 16GB (1600 Mhz)

I have no problem with X-Plane on Steam, but with all shooters and other games with a bad morale. To prevent our family from aggressive games we use an internet-filter. And that filter blocks Steam because with their site it is all or nothing. In our case: nothing. Thats why I hope X-Plane will also be available on the traditional way.

Yep, and the sticky tires when you taxi on terrain also. But it is still going strong.

For me or becomes a problem, if Steam becomes the only option. As long as I can get X-plane on the traditional way, it is okay.

A Cloud Detail of 70% is high, but according to the other setting I should expect at least twice the fps you have. On the other hand, Ben Supnik still has to solve fps-related issues with AMD-cards in X-Plane 10.30,

Yes braking gives sometimes a lot of trouble. It looks like that while pressing B not 100% of the brakes is released and after pressing B another time B the brake pressure returns not to 100%. It seems that this key gives trouble al the way. (You can see this behaviour after selecting the variables around braking in the data input & output screen [settings]). Sometimes after many B presses the brake pressure goes in the direction of zero and you can move. Pressing V is more reliable in this case. (Or was V the problem and B okay, I don't know exactly anymore ... it becomes time to release the brakes of the MU shortly...). I don't even know if releasing and setting the prake by mouse had the same problem or not. I hope that this bug get solved one day.

Hereby the results of the fps tests of X-Plane I have done with my system this evening. The specs of my PC are: CPU: Intel i5 3570K @ 4,5Ghz Memory: 16GB @ 1600Mhz GPU: GTX 770 4GB It seems that X-Plane 10.30 performs better on heavy settings and poor om low settings. Maybe that users with a slow system will have problems with their fps, while power users see a better performance. Nvidia solved the nasty bug with driver 337.88, but performance is not an improvement for me. OK there is a performance gain with test 1 on X-Plane 10.30 but that are settings I never use.

Thanks for the reaction, but are there GoFlight users out there. Verstuurd vanaf mijn HTC One S met Tapatalk

I consider buying some Go-Flight modules. Mainly the following modules: - GF-LGT II Landing Gear and Trim Control Module - GF-RP48 Push Button Rotary At the moment i use my buttons of the saitek throttleconsole while using rudder/aileron trims it is always near miss. I also use a Saitek trim, a very nice and precise instrument, but problematic when turning of the autopilot. In that case touching the trim will cause a great unwanted attitude change. I hope that the GoFlight modules have a better solution for the mentioned problems. A possibele drawback maybe the point that GoFlight is not compatible with complex add-ons as the Saab 340a. Are there users who have experience with GoFlight, please let me know.

Get alpilotx HD mesh: www.alpilotx.net. Probably you will der the lakes, or else be patiënt. Verstuurd vanaf mijn HTC One S met Tapatalk

Good news, this is (and hopefully was) one of the frustating things in X-Plane.

I have made some screenshots of the construction vehicles. It seems that the Netherlands is full of building activities everywhere I see flashing lights of the bulldozer. Checking OSM, and yes that are planned new residential area's. I see however that most places are still only planned with no building activity. Is it possible to turn the lights of from the bulldozer, because it looks odd at the moment.

1. Better weather engine (realistic wind, less thunder and lightning, leed turbulence, now too exxagarated) 2. Better atc. 3. Better framerates 4. Full map, instead of one part 5. Intiutive manipulators 6. Environmental sounds 7. Better groundhandling of planes (planes react top string on crosswind)