![]() entirely by keyboard) using standard keyboard shortcuts. You can now navigate around DRT without using a mouse (i.e.Added dozens of new keyboard shortcuts.You can now edit dataref values directly from the search window.Thanks to for help identifying this and solving a related bug. There's also a workaround to a longstanding crash involving the Bell 407 helicopter. If you use keyboard shortcuts, you'll find getting around DRT to be much easier. This release has a ton of minor changes to the interface that improve the workflow substantially. Some Linux systems still have problems running DRT I recommend that Linux users compile their own plugins for now if you run into this issue.When viewing array datarefs in the dataref edit window, the number of elements shown varies proportionally to window size, instead of overflowing onto the rest of the screen.With this change, slightly more array dataref elements should be visible in results. When viewing array datarefs, the algorithm that determines how many array elements to display has been updated to compute more precisely what can be fit into the space available.This allows more data to be displayed within the same amount of space. The font used to display results has changed from a monospace to a proportional font.For details on how this works, see the documentation in doc/API.md. Other plugins can use DRT's search when the DRT plugin is also installed. An API is now available to other plugin developers.īuy a faster CPU! :-) DRT is written in a highly optimized and efficient manner however, it does a lot of work, and that work takes CPU time.This will be the final release to support X-Plane 10.To identify datarefs that are slow to read, use a CPU profiler (I use X-Code Instruments). In X-Plane 11, I'd recommend adding these slow datarefs to the ignore file: sim/airfoils/afl_cd You can do this buy creating a file called X-Plane 11/Resources/Plugins/drt_ignore.txt, and list the datarefs you want to ignore there. Ignore datarefs from other plugins that are slow to read. DRT does stop reading datarefs completely when all windows are closed you should not lose any FPS at all when all windows are closed. Here are the best ways to make sure that DRT is having the smallest impact on your FPS:Ĭlose all DRT windows when you aren't using them. It takes CPU time to actually do what DRT does this is why you're losing FPS. This takes time moreover, it takes time for other plugins and for X-Plane to compute the dataref values (which is what actually takes most of the time). FAQ: DataRefTool causes me to loose FPS! Why?ĭRT reads datarefs every frame in order to detect changes to values. ![]() The Bell 407 problem is being tracked in issue #33 in this repository. To work around this, create a file called X-Plane 11/Resources/plugins/drt_ignore.txt, and add the following lines to the file: B407/Lights/CL1 If you're flying the Bell 407, there is a known issue with this aircraft where reading some datarefs triggers an immediate crash. FAQ: Using DRT with the Bell 407 causes X-Plane to crash This will cause DRT to never read the value of the dataref, even if it does come up in search results. If you can figure out which dataref caused the crash, the best way to work around this is to add the name of the dataref to a file called X-Plane 11/Resources/plugins/drt_ignore.txt. (If you're a developer, the best way to do this is to run X-Plane in a debugger and look at the backtrace of the crash- if you see RefRecords::update() in the backtrace, this is likely what happened.) Sometimes, they haven't fully been debugged, and may crash. FAQ: Using DRT causes X-Plane to crashĭRT reads every dataref published by every aircraft and plugin, on every frame of the simulation. This way, X-Plane itself will tell DRT about all datarefs it knows about. Before you do this, ensure that the DataRefEditor plugin is not installed. Turn on "Impersonate DataRefEditor" on the plugin menu inside X-Plane.Have your plugin send DRT a message with as described above in "Adding custom datarefs".If this is an aircraft, add a file called "dataref.txt" inside your aircraft directory with a list of datarefs and commands, one on each line.This might not work if your dataref is in an encrypted Lua file or something, so you have several options:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |