Re: [Flightgear-devel] RE : Did anyone test the 2.6.0 release on Windows 7 64 Bit?

2012-02-22 Thread kreuzritter2000
Am Mittwoch, den 22.02.2012, 08:51 +0100 schrieb Frederic Bouvier:

 1. did these problem occurs in the release candidates or are specific
 to the final version ?

b89717f9acf01d154c868afadf39b89f  Setup FlightGear 2.6.0.exe


 2. We know that you didn't install in Program Files but we don't
 know where exactly. Could there be a special german character in the
 path, or any non purely ascii character ?

E:\Games\FlightGear


 3. what happen if you install in Program Files as suggested by the
 installer ?

Don't know, didn't try that.


 4. Did you install the 64bit binaries or have forced the 32bit
 install ?

This was another confusing thing in the installer.

There was no help given and i wondered why i should force the installer
to install the 32 Bit version on a 64 Bit system.
So i decided to take the default setting and because the force
installer to install the 32 Bit version was marked i took the 32 Bit
version.


I suggest to split the windows version in a 32 Bit and 64 Bit
installerpackage or give more detailed information why a 32 Bit version
should make sense on a 64 Bit system.
 



 5. Can you find the flightgear.org directory in \Users and check
 that fgrun.prefs has write privileges ?

This directory was created after i started FlightGear first time in the
users:

%APPDATA%\Roaming\flightgear.org

Keep in mind, that i installed as admin but didn't start FlightGear as
admin!

So the installer put the files in

Users\Administrator\AppData\Roaming\flightgear.org

but this is useless for other user accounts, it's not used by them.


For things like that i suggest do put a default config file created by
the installer as read only in the directory where fgrun is.
And when fgrun ist started it should check if there is already a user
config file in 
%APPDATA%\Roaming\flightgear.org

available.

If not, then it should read the default config files set by the
installer that were installed in fgrun's directory like i suggested and
then create a new one in 

%APPDATA%\Roaming\flightgear.org


I also want to mention, never use direct addressing 
instead always use Environment variables to check the locations of
Programm files, Windows or Users.

Wrong (direct addressing):
  C:\Program files
  C:\Windows 
  C:\Users

Correct (indirect addressing via Environment variables):
  %PROGRAMFILES%
  %WINDIR%
  %HOMEPATH%

Read here for more informations:
http://en.wikipedia.org/wiki/Environment_variable#Default_Values_on_Microsoft_Windows
  

You can't expect to have the users data in:
C:\users\username\

My users directory is for example called home, not users and it is
in:
F:\home\myusername\

So the only correct way to get there is via:
%HOMEPATH%





  The save button is only there to save another set of options and it's
 normal that a file name is requested. For the current set of options,
 it goes to flightgear.org\fgrun.prefs but this file should be
 writable. It is created at install and contains the default path that
 you shouldn't have to set by hand.

The default path is the admins user directory when installed as admin.
It shouldn't belong there if other users should be able to read these
config files!
So put them in the program directory of fgrun as mentioned before or in
a shared user config directory and then check at start if a user has its
own config files, and if not, read them from the programm directory or
the shared user config directory like mentioned before.
And after that, create one in the user's directory and use this for
writing new settings data to it. Never write the data for daily use to
somewhere else, only in the users's directory, never the programm
directory.

Best Regards,
 Oliver C.





--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] RE : Did anyone test the 2.6.0 release on Windows 7 64 Bit?

2012-02-21 Thread Frederic Bouvier
Hi,

I am away from my computer so I can comment specifically any point, but I have 
few questions : 

1. did these problem occurs in the release candidates or are specific to the 
final version ?

2. We know that you didn't install in Program Files but we don't know where 
exactly. Could there be a special german character in the path, or any non 
purely ascii character ?

3. what happen if you install in Program Files as suggested by the installer ?

4. Did you install the 64bit binaries or have forced the 32bit install ?

5. Can you find the flightgear.org directory in \Users and check that 
fgrun.prefs has write privileges ? The save button is only there to save 
another set of options and it's normal that a file name is requested. For the 
current set of options, it goes to flightgear.org\fgrun.prefs but this file 
should be writable. It is created at install and contains the default path that 
you shouldn't have to set by hand.

Regards,
-Fred


kreuzritter2000 kreuzritter2...@gmx.de a écrit :

Yesterday i tried to run the new FlightGear version on Windows 7 64 Bit
Prof and it run awful.


There are several fatal major bugs in this release i never had before,
though i used WinXP 32 Bit in the time of the older releases before and
not Win7 64 Bit, so i am not sure if this is win7 related.


I installed FlightGear in another folder than C:\Programs files as
admin and run FlightGear with normal user privileges. 
This might be an important information to reproduce some of the bugs.




I am here on a linux system now, so i can't test it again, but here is a
small listing of some of the bugs and usability issues i can remember
from yesterday:

1. FGRun can't find the progamm, scenery and data folders, i have to set
them manually at the first start. That shouldn't be the case,  FGRun
should know where to search for the files after FlightGear has been
installed. An inexperienced computer user would give up here and
uninstall FlightGear.  

2. It is impossible to set the Terrasync folder in FGRun, the button to
set the terrasync folder has no function. The terrasync mode can't be
used when there is no directory set.
BTW, terrasync should use the user directory by default, it's evil to
use the progamm folder for that when a user has limited privileges on
that directory. Usability hint: When there is a default directory set
there is no need to annoy the user with asking the user for a directory
location. I suggest to use %APPDATA%/Roaming/flightgear.org/terrasync as
default location. If users don't like that, they should be able to
change it after installation. But setting a default location is a must
in my opinion to improve usability.

3. FGRun doesn't use the user folder to save the settings, instead it
asks me where to place it. That's bad usability.

3. Several 3d Models (777-200, F-14b and others) aren't displayed.
They're missing in the sim and in FGRun.

4. In flightGear the 3d cockpit controls do not work. For example in the
b1900d clicking on them has no effect. In the past on earlier releases
that worked.

5. Worst Bug. The sim has strange flickering effects, the result is that
the clouds are not displayed. They flicker sometimes up, but only in 1-4
of 60 frames. (My system: Geforce GTX 550 Ti + driver version 280.26)
The console shows some error message about OpenGL and a function, but
the text is cut, so there's no real info about it.

6. BTW this is only a minor usability issue, but i'll mention it here
for for the sake of completeness. FGRun has long loading times to
display the 3d aircraft models. In my opinion that is too long for a
selection list like that.


In my opinion bugs 3, 4 and 5 are the worst in that list and 1 and 2 are
serious usability issues all of them harm the reputation of FlightGear
more than a new release version with new features do good to it.
I can't recommend to offer FlightGear in that condition for download for
windows users.
Why where there no release candidates or beta releases? Bad release
candidates or beta releases do not harm a project so badly like a real
release with fatal bugs does.


Best Regards,
Oliver C.






































--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.