|
|
|||||||
| IL-2 Sturmovik The famous combat flight simulator. |
 |
|
|
Thread Tools | Display Modes |
|
#12
01-09-2011, 03:20 PM
|
||||
|
||||
Quote:
 : Following your suggestion I moved the BU0836A up to ID3 and Il-2 still would not recognize it (I've even created a correct entry in settings.ini manually)...Using Windows7, 32bit, and both my BU0836As are working perfectly with the application feeding Il-2 via devicelink. Mhm, could this be an issue worth it's own thread? 
|
|
#16
07-17-2011, 05:17 PM
|
|||
|
|||
|
Question: is this also related to the ability of having the data output for both engines working via updspeed?
New to things with the game as well as the forums dealing with it. I was looking at the devicelink threads online here and elsewhere and it seems that to the best of what I can figure out, its not possible........................but the threads and posts with more details on devicelink and updspeed are older then the most current patch which does have the axes for the multi-engines. I really liked the P-38 and as such wanted to focus on flying it. Because of how the gauges can be outputted to another display via device link I wanted to see if I could also have the gauges for both engines on the display. Not intended to highjack, just seemed better here then a new thread
|
|
#17
07-17-2011, 06:32 PM
|
||||
|
||||
|
Quote:
 Your question: The DeviceLink works on multiple machines on get() just like on set() (see DeviceLink.txt in your IL-2 directory): Select engine #1 (command 123), then call get() for Power and Proppitch..., select engine #2 (command 125), repeat query. Does this answer your question? Artist
|
|
#18
07-18-2011, 02:16 AM
|
|||
|
|||
|
Artist, I'm looking to be able to create a updspeed gauge setup that includes seperate data for each engine.
From searching it not sound like anyone was able to do this................but again, most of the threads dealing with the gauges on a second display are older then the newest patch. Best as I could tell the device link txt has not changed from 2004 and it seems like the few people who went a little deeper into making updspeed gauge setups mentioned that multi-engine data for gauge display was not working........................newer patch has the CEM abilities for the multi-engines...............so I was wondering if that had an effect on the issue. Device link txt looks like it has not changed/edited since 2004 on my install. Looking at it I see what you descibe above so what I sounds like I need to do is have something like: Select engine #1 (command 123), then call get() for rpm and manifold..., select engine #2 (command 125) then call get() for rpm and manifold...............same as for water temp and oil temp/pressure?
|
|
#19
07-18-2011, 07:35 AM
|
||||
|
||||
|
Jack,
that is what I would do  . See: As all get methods that deliver information on the status of the aircraft are disabled when flying online, I never used them. In YaDeLi I used only set methods and for multiple engine support I did just that: When you assign power for engine #1 to axis A and for engine #2 to axis B YaDeLi would, when you move an axis, select the attached engine first and then send the power change command...The get methods for your information seem to behave differently, as their get method has a parameter for engine index (see DeviceLink.txt) - so you would not have to select the engine first. Concerning DeviceLink.txt, Team Daidalos, and multiple engine support in version 4.10: The capabilities of DeviceLink haven't changed since 2004 (I guess) and Team Daidalos has not changed anything there - which is not that bad as we can workaround the limitations. Artist
|
|
#20
07-18-2011, 09:45 PM
|
|||
|
|||
|
Artist, thanks for the information and sticking with me on the noobish questions and going a little off course.
I'm going to spend some more time reviewing the devicelink txt while also checking the device link tips and question thread over at ubi and see if I can come up with something that works. Again, thank you
|
|
|
|
Linear Mode
