Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[fly77]

Finally I have learned to fly the bk117 helicopter by using a lot the trim and setting joystick sensivity to high and a deadzone to narrow.
Then I made some modification to the javascript to set up zoom (see code below for the core of it). Then as I pressed +/- keys on numpad to zoom keys while flying the bk117 heli up came this screen while zoom does not work..
the +/- keys seem associated to something different for the bk117..
What is its purpose ? Could I program similar nice sliders and buttons on my own ..look like java buttons?

Code: [Select]


function update_frame(dt){

  fov_cockpit_zoom = 81.8;
  this.register_axis("air/sensor/fov_zoom", {minval:0, maxval:1, vel:1, center:0}, function(v){
    var dec2int = v*48;
    var integer = Math.floor(dec2int);
    var string = 81.8 - integer.toString();
    fov_cockpit_zoom = string;
  });
 
   if (this.get_camera_mode() == 0){
    ot_world.set_camera_fov(fov_cockpit_zoom);
  }

[cameni]

It's an old window used for initial setup. Otherwise it's a normal html window.

What you can do is make such an html, set the path in config (see T817 script, property config returned from init_chassis).
The window will open when pressing the key bound to the ot/player/open_config action.

$object in the html corresponds to the vehicle interface there, but you should see it in the example.

[fly77]

Thanks a lot ! Interesting. Will try it.
By the way I found the reason why it came up. I put the register axis command in update frame instead of initialize_reload.

[Revolver]

Hi Marco!

It becomes very interesting and of all worthwhile, if there can save under each flight object its own settings.
If you understand what I mean ...

Gruß,
Stefan

[fly77]

yes I understand well what you mean. Will try if I can get it to work to make something useful

[fly77]

It's an old window used for initial setup. Otherwise it's a normal html window.

What you can do is make such an html, set the path in config (see T817 script, property config returned from init_chassis).
The window will open when pressing the key bound to the ot/player/open_config action.

$object in the html corresponds to the vehicle interface there, but you should see it in the example.

Sorry how to bring up the config window for the t817 ? which key ?

[KW71]

"t" (to config the suspension parameters).

[fly77]

Showing off my fleshly acquired Heli-flying skills doing an aircraft carrier landing. Joystick set to sensitive and low deadzone in outerra + using a lot of trim.
Aircraft carrier and bk117 heli mod are work in progress.

[aWac9]

great, fantastic .. great contribution.
waiting for publication ..

[Revolver]

oha!   cool! Sehr gut gemacht, Marco!

[fly77]

danke Stefan ! Will publish something in july

[fly77]

I am trying to set up a "config.html" file where I'd like to set other parameters besides wheel_params. That is I'd like to set some of the variable values used in the javascript...for instance in case of the Heinkel...set the number and type of ammunitions. Is it possible through such a config window or do I need to go another way (for instance I am thinking I could use a canvas based menu and use key events to navigate through the menu and incr/decr individual values).
Using the config window would be much more elegant. Is it possible ?

[fly77]

That window to set initial aircraft parameters looks very interesting... So by following the t817 example I decided I try adding a config folder to the cessna. I found that the necessary files are in outerra /anteworld/www folder

So I created a "config" folder inside the Cessna folder and added inside the "aircraft.html"  +  "ot-slider-raw-css.css" + "outerra-theme.css" files + the "css" and "js" folders copied from www folder as they seem needed.
Then modified the javascript of the Cessna including a  code line   : return {config: "config/aircraft.html"}; to the initialize-reload function.

Then by pressing key "t"  I can open the config window from within the Cessna and set the sliders..also closing the window leaves the plane alive.The only problem is that I do not see any effect on the plane.
Also each time I touch a control in the opened config window  outerra gives me FATAL errors in the eng_log

Code: [Select]

23:09:47.036 FATAL: (c4e) [0630/000947:INFO:aircraft.html?width=400&height=300(31)] onfocus
23:09:47.036 FATAL: (c4e) [0630/000947:INFO:aircraft.html?width=400&height=300(31)] onfocus
23:09:49.929 FATAL: (c4e) [0630/000949:INFO:aircraft.html?width=400&height=300(31)] onfocus
23:09:49.930 FATAL: (c4e) [0630/000949:INFO:aircraft.html?width=400&height=300(31)] onfocus
23:09:51.345 FATAL: (c4e) [0630/000951:INFO:aircraft.html?width=400&height=300(31)] onfocus
23:09:51.345 FATAL: (c4e) [0630/000951:INFO:aircraft.html?width=400&height=300(31)] onfocus
23:09:55.007 FATAL: (c4e) [0630/000955:INFO:aircraft.html?width=400&height=300(35)] onblur
23:09:55.007 WARNING: (c4e) [0630/000955:ERROR:aircraft.html?width=400&height=300(53)] Uncaught TypeError: Object #<Object> has no method 'on_scenario_close'

I guess FATAL is not good 

Then I found another way to bring up the config window which is written actually in the outerra help menu..where it says key tilde for initial airplane configuration..on my keyboard this is actually key "@" and it indeed opens the config window of the cessna and now as I touch the sliders indeed they have an effect on the plane position/attitude...BUT as soon as I close the window the Cessna position is frozen into place !!
While some parts of it still seem to react (for instance the joke still reacts to my joystick and flaps values ract to keyboard)..but the position is frozen. The plane can't be reactivated in any way while outerra is still working. Even ctrl+alt+R doesn't  work. By looking at the eng_log I have the following error messages which I don't understand

Code: [Select]

23:07:48.268 FATAL: (c4e) [0630/000748:INFO:aircraft.html?name=Aircraft%20Scenario&width=800&height=222&transparent=true(31)] onfocus
23:07:48.268 FATAL: (c4e) [0630/000748:INFO:aircraft.html?name=Aircraft%20Scenario&width=800&height=222&transparent=true(31)] onfocus
23:07:50.674 FATAL: (c4e) [0630/000750:INFO:aircraft.html?name=Aircraft%20Scenario&width=800&height=222&transparent=true(31)] onfocus
23:07:50.674 FATAL: (c4e) [0630/000750:INFO:aircraft.html?name=Aircraft%20Scenario&width=800&height=222&transparent=true(31)] onfocus
23:07:53.257 FATAL: (c4e) [0630/000753:INFO:aircraft.html?name=Aircraft%20Scenario&width=800&height=222&transparent=true(35)] onblur

So the question is how to "make it react to the sliders" and "keep plane alive"  ?   Any hint ?

[cameni]

Those fatals are actually harmless forgotten logs. It's the TypeError you should be worried about. Any object surely should not be named #<Object> ...

[fly77]

OK I deleted the line "scenario.on_scenario_close()" inside the aircraft.html  that created the type error..now the window closes without giving the type error but still no response from plane when pressing "t" and still position frozen when pressing tilde (or rather @ for me). Is return {config: "config/aircraft.html"} to be placed at the end of initialize_reload or elsewhere and are there some variables that I need to define inside the plane's javascript (like wheelparams for vehicles) so that the return {config: "config/aircraft.html"}  has some effect ?  Like for instance "altitude_asl" that is inside the html ?

Code: [Select]

function close_window() {
                window.close();
                scenario.on_scenario_close()
            }