I've tweaked the DR400 to show its ASI in knots. Does anyone know how to put a clock in one of those blank spaces? Do you have some generic stuff I can use Jet-Pack (IPACS) . I mainly like to fly by pilotage and VORs and a clock is pretty handy in these situations.
Clock in the Dr400
-
-
- Official Post
Hi Phil,
you can do that, just copy paste the code sections from clock of the default cessna 172, change the texture target coordinates, add it to the render list (if the texture you are rendering to is already in use or make a new one if this texture has not been rendered to before) and you should have a working clock...
Alternatively you can adjust the 3D model, reassign textures to the blank area and then render to just that new texture.
-
Hi Phil,
you can do that, just copy paste the code sections from clock of the default cessna 172, change the texture target coordinates, add it to the render list (if the texture you are rendering to is already in use or make a new one if this texture has not been rendered to before) and you should have a working clock...
Alternatively you can adjust the 3D model, reassign textures to the blank area and then render to just that new texture.
Great thanks. So this can be done without running the SDK conversion potentially? Clock related things seem to appear in various places in the c172.tmd. I'll find them all and try to put them in the right places (or can I bundle them all once I've tracked them down) and see what happens.
Am I right in thinking I only need to run the conversion if I need to bring in a new texture?
EDIT: OK tried that. Extracted the following clock related stuff, put it inside the [DynamicObjects] section as one block. I figured it would be in the wrong place and need prettying up, but instead it crashed the DR400 and reset my main.mcf
-
- Official Post
The tmd has three sections, you can't put objects that belong to the graphics section into the dynamics seciton.
all after
// -------------------------------------------InstrumentLightControl------------------------------------------
needs to go into the graphics section....
-
- Official Post
but instead it crashed the DR400 and reset my main.mcf
... the tm.log file usually tells you why aerofly crashed. When aerofly crashed loading a model it just resets the main config as a precaution. Then aerofly is at least usable again
-
Great thanks Jan. I guess there's no short cut to tracing back through all these dependencies and including them ....if I can find them.
Code
Display More23.20-tmimage: loading model dr400... 23.20-tmmodelmanager: model: (name='dr400') (directory='C:/Users/oculus/Documents/Aerofly FS 2/aircraft/dr400//') 23.20-tmimage: loading configfile 'C:/Users/oculus/Documents/Aerofly FS 2/aircraft/dr400///dr400.tmc' 23.20-tmmodule: contact points 3: (1.371 0.000 -0.545 r=0.180) (-0.260 1.212 -0.570 r=0.160) (-0.260 -1.212 -0.570 r=0.160) 23.51-tmimage: loading dynamics begin 'C:/Users/oculus/Documents/Aerofly FS 2/aircraft/dr400///dr400.tmd'... 23.52-tmcollision: ERROR: duplicate object 'Clock' 23.52-tmcollision: ERROR: duplicate object 'UniversalTime' 23.52-tmcollision: ERROR: duplicate object 'UniversalTime' 23.52-tmcollision: ERROR: object 'TemperatureVoltage' not found 23.52-tmcollision: ERROR: property 'TemperatureVoltage.Output' not found 23.52-tmcollision: ERROR: object 'MultiValueTemperatureVoltage' not found 23.52-tmcollision: ERROR: property 'MultiValueTemperatureVoltage.Output' not found 23.52-tmcollision: ERROR: geometry 'ButtonSelect' not found 23.52-tmcollision: ERROR: cannot link ' ButtonSelect ' 23.52-tmcollision: ERROR: geometry 'ButtonDatVolts' not found 23.52-tmcollision: ERROR: cannot link ' ButtonDatVolts ' 23.52-tmcollision: ERROR: geometry 'ButtonControl' not found 23.52-tmcollision: ERROR: cannot link ' ButtonControl ' 23.52-tmfile_properties: property |InputEnable| not found in this context |graphics_input| 23.52-tmfile_properties: property |InputVoltage| not found in this context |graphics_input| 23.52-tmfile_properties: property |AddLoad| not found in this context |graphics_input| 23.52-tmfile_properties: property |MinimumVoltage| not found in this context |graphics_input| 23.52-tmfile_properties: property |RatedCurrent| not found in this context |graphics_input| 23.52-tmfile_properties: property |Input| not found in this context |graphics_input| 23.52-tmfile_properties: property |Input| not found in this context |graphics_input| 23.52-tmfile_properties: property |Running| not found in this context |graphics_input| 23.52-tmfile_properties: property |InitialTime| not found in this context |graphics_input| 23.52-tmfile_properties: property |Input| not found in this context |graphics_input| 23.52-tmfile_properties: property |InputEnable| not found in this context |graphics_input| 23.52-tmfile_properties: property |Range| not found in this context |graphics_input|
-
- Official Post
In your text file that you uploaded you have a block of code repeated twice, that's why it tells you duplicate object...
I've looked into the tmd file of the dr400 an it appears it already has a clock in the physics section...
and in the graphics section just add the codeCode
Display More<[graphics_sec_to_hms][Watch][] <[string8][Input][UniversalTime.Output]> > <[texture_animation_numeric_display][LcdClockHours][] <[string8][TextureName][display_source_light]> <[string8][Input][Watch.Hours24]> <[tmvector2d][TargetPosition][ 16 25 ]> <[tmvector2d][TargetSize][ 25 38 ]> <[tmvector2d][TargetScale][ 256 256 ]> <[float64][TargetStride][ 27 ]> <[tmvector2d][SourcePosition][ 0 0 ]> <[tmvector2d][SourceSize][ 64 92 ]> <[tmvector2d][SourceScale][ 1024 1024 ]> <[float64][SourceStride][ 64 ]> <[int32][Digits][2]> <[bool][ShowLeadingZeroes][true]> > <[texture_animation_numeric_display][LcdClockMinutes][] <[string8][TextureName][display_source_light]> <[string8][Input][Watch.Minutes60]> <[tmvector2d][TargetPosition][ 80 25 ]> <[tmvector2d][TargetSize][ 25 38 ]> <[tmvector2d][TargetScale][ 256 256 ]> <[float64][TargetStride][ 27 ]> <[tmvector2d][SourcePosition][ 0 0 ]> <[tmvector2d][SourceSize][ 64 92 ]> <[tmvector2d][SourceScale][ 1024 1024 ]> <[float64][SourceStride][ 64 ]> <[int32][Digits][2]> <[bool][ShowLeadingZeroes][true]> > <[texture_animation_numeric_display][LcdClockSeconds][] <[string8][TextureName][display_source_light]> <[string8][Input][Watch.Seconds60]> <[tmvector2d][TargetPosition][ 143 25 ]> <[tmvector2d][TargetSize][ 21 32 ]> <[tmvector2d][TargetScale][ 256 256 ]> <[float64][TargetStride][ 23 ]> <[tmvector2d][SourcePosition][ 0 0 ]> <[tmvector2d][SourceSize][ 64 92 ]> <[tmvector2d][SourceScale][ 1024 1024 ]> <[float64][SourceStride][ 64 ]> <[int32][Digits][2]> <[bool][ShowLeadingZeroes][true]> >
and in the list:
Code
Display More<[texture_animation][RadioTexture][] <[string8][TextureName][display_color]> <[string8][RenderList][ DisplayBackground.Render COM1FrequencyDisplay.Render COM1StandbyFrequencyDisplay.Render NAV1FrequencyDisplay.Render NAV1StandbyFrequencyDisplay.Render DisplayTransponderNumber.Render DisplayTransponderAltitude.Render DisplayTransponderATLFLIndicator.Render DisplayTransponderSTBYIndicator.Render OBSIndicator.Render OBSBarIndicator.Render ]> >
add:
LcdClockHours.Render
LcdClockMinutes.Render
LcdClockSeconds.Render
then there should be a numeric display somewhere on the texture that shows the time...
I've not really tested this particular example but it's not too complicated. All left to do is find out the texture coordinates (lower left corner) where your clock hours, minutes and seconds should go -> TargetPosition
-
Thanks Jan. I was going to give up, but I can't do that now after all this help. Sadly still no clock. I've been staring and staring but can't see anything. i put the texture/graphics stuff just before sound objects and added the LCD render code. No errors in tm.log but no new visuals either.
Might they be completely outside the area of the radio kit and I need to put some numbers in that are in the right ballpark before fine tuning position?
-
- Official Post
Might they be completely outside the area of the radio kit and I need to put some numbers in that are in the right ballpark before fine tuning position?
There is nothing like that in aerofly.... you can copy the target position, size and scaling from the navigation stuff and use it for the clock, then it should render the clock overtop the navigation "stuff"