Print

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

[mustang60348]

Code: [Select]

<aerosurface_scale name="Flap Position Normalizer">
              <input>fcs/flap-pos-deg</input>
              <domain>
                <min>0</min>  <!-- Flaps actual minimum position -->
                <max>30</max>  <!-- Flaps actual maximum position -->
              </domain>
              <range>
                <min>0</min>  <!-- Flaps normalized minimum position -->
                <max>1</max>  <!-- Flaps normalized maximum position -->
              </range>
              <output>fcs/flap-pos-norm</output>
            </aerosurface_scale>
I also have this in mine to normalize the flap movement

[ddenn]

Yes, I have it too.

[angrypig]

Version 0.7.13.3512
...

• JSBSim updated to the latest version

...

After this update the flaps deploy time setting is not working. Is there a new way to work with flaps? That how it worked on previous versions:

Code: [Select]

  <channel name="Flaps">
   <kinematic name="Flaps Control">
     <input>fcs/flap-cmd-norm</input>
     <traverse>
       <setting>
          <position>  0 </position>
          <time>      0 </time>
       </setting>
       <setting>
          <position> 30 </position>
         <time>      5 </time>
       </setting>
     </traverse>
     <output>fcs/flap-pos-deg</output>
   </kinematic>Now with the same time setting flaps deploy time is 1 second instead of 5, and changing this value has no effect.

There was no change from my side to flaps movement. Can you show me the entire source for channel Flaps? I checked c172 flaps and it works as it should the first 10 degrees are moving down for 2 seconds, it is probably something in your channel definition or some change in JSBSim.

[ddenn]

You mean this part?

Code: [Select]

  <channel name="Flaps">
   <kinematic name="Flaps Control">
     <input>fcs/flap-cmd-norm</input>
     <traverse>
       <setting>
          <position>  0 </position>
          <time>      0 </time>
       </setting>
       <setting>
          <position> 30 </position>
          <time>      5 </time>
       </setting>
     </traverse>
     <output>fcs/flap-pos-deg</output>
   </kinematic>

   <aerosurface_scale name="flap normalization">
      <input>fcs/flap-pos-deg</input>
      <domain>
        <min>  0 </min>
        <max> 30 </max>
      </domain>
      <range>
        <min> 0 </min>
        <max> 1 </max>
      </range>
      <output>fcs/flap-pos-norm</output>
   </aerosurface_scale>

  </channel>

[angrypig]

I just modified the C172 FDM to 30deg for 5sec and it works its 1.66s for 10degs... try to compare your FDM to C172's FDM...

[ddenn]

Yes, I tried to change time setting again and it works.. My bad, something messed up somewhere

EDIT - found the problem, after upgrade I have a lot of FPS, and it turns out that jsbsim animation work incorrectly (too fast) with FPS more than 30 (I have 100-200). Setting Vertical Sync option to half-refresh fixes the problem (of course that's a bug).

[ZeosPantera]

Too many frames is never a problem.

[Andy]

Hi there,
i just tested the latest build for the first time on Linux with WINE.

Installation went without problems. Starting the game mentions that it cannot get information of my graphics hardware but when i ignore that dialog by clicking "yes" the game starts fine.

First in the game i see graphical artifacts but i can overcome them by scrolling the mouse wheel up and then fly in the orbit. After that i can see the globe and it looks fantastic. (I can only see one half, the other half is white)

Sadly, when trying to reach the ground of the planet the game crashes (Segmentation fault) without any error message.

Did someone manage to start and play the game in WINE on Linux?

----
My System details:
Archlinux 64 bit (but a 32 bit wineprefix)
8 GB Ram
Nvidia GeForce 275 GTX (Driver 313.18)

[cameni]

Version 0.7.13.3530

• random rocks
  
• 2048px terrain textures, added texture resolution slider in terrain cfg
• lowered tree branches at forest borders
• modified tree texture to give a curved trunk appearance
• fixed video color range and contrast issue (full range to HDTV)
• finer ufo speed stepping
• smoother grass lighting
• finer dirt patch borders

Random rocks are like in the .
Default texture detail level is using 512px textures, finer levels use 1024 and 2048. There's still some precision issue at 2048px on steeper slopes.

[deathevor]

Nice,

Not sure this is related to the issue you've mentioned, but I have this kind of glitches on snow -

[Midviki]

After I updated, got a blue screen , pc restarted I tried to enter outerra again... I got that.

What to do?

[Jagerbomber]

It looks like rocks have been added even to areas that were already previously download? Yes???

It can be hard to tell without the map up, but some of them are really massive! Holy crap!
(And even cause themselves to have their own trees)
Some of them could almost be mountains themselves... (Well... New England mountains...  )

Also, just noticing now that, yes, the map arrow rotation is synced with the vehicle your are driving, but the actual arrow position is still set to the camera location, so if you change your camera to outside the vehicle and zoom out or swivel around, the arrow position moves with the camera and not the vehicle (though still rotates with the vehicle).  It should probably be all completely synced with the vehicle.

[ZeosPantera]

It can be hard to tell without the map up, but some of them are really massive! Holy crap!
(And even cause themselves to have their own trees)
Some of them could almost be mountains themselves... (Well... New England mountains...  )

THIS...



is not a rock..

My god there are too many of them also.

[cameni]

After I updated, got a blue screen , pc restarted I tried to enter outerra again... I got that.

What to do?

Update drivers, attach eng.log.

[cameni]

It can be hard to tell without the map up, but some of them are really massive! Holy crap!
(And even cause themselves to have their own trees)
Some of them could almost be mountains themselves... (Well... New England mountains...  )

THIS... http://i3.minus.com/iJufoiCglmrjV.jpg is not a rock..

My god there are too many of them also.

Our beloved ATI 4000 series at it again. This is what I see when I jump into your photo:

It looks like rocks have been added even to areas that were already previously download? Yes???

These rocks are procedurally generated & placed atop of the terrain. The size of the rocks and their frequencies are all adjustable, will be tuned better in time. Don't count that they will stay where they are now.