Hi Geoff, 

OK. the SG and FG versions were from git on the 15th as well as the fgdata as 
of last night 

the 3rd party was the same as you noted. 
\3rdparty - fgfs-win32-VS100-3rdParty+OSG-20120411.zip 

Thought I mentioned that in an earlier email. No problem, bears worth repeating 
to make certain 

Looking over your comments, it might be my install of the OSG stuff that is 
causing the problem. Took the "easy" way of sticking fgfs.exe in with the 3rd 
party libraries, guessing what is missing is the OSG plugin or a path to it. 
I'll look there first. Sometimes the error msgs are not very clear to newbies. 

We'll get there... 

John 



----- Original Message -----
From: "Geoff McLane" <ubu...@geoffair.info> 
To: "FlightGear developers discussions" 
<flightgear-devel@lists.sourceforge.net> 
Sent: Monday, April 16, 2012 8:12:30 AM 
Subject: Re: [Flightgear-devel] FGbuild for MS Windows 

On Mon, 2012-04-16 at 12:53 +0000, castle...@comcast.net wrote: 
> Complains about not finding a plugin to read objects from file 
> c:/fg-2.7.0/fgdata/xxxxxx from the gitgo. 

Hi John, 

Well it seems some good news and some 
bad news ;=)) 

Missing plugin... yes this is quite common, 
unfortunately ;=(( Suggests some problems 
with the OSG used, or something... 

But you give NO INFORMATION on exactly what you 
built!!! Exactly WHAT 3rdparty stuff you 
used? Versus what did you build from source? 

I built Release SG/FG yesterday, git 15th like you, 
in a root c:\FG\14, using :- 

\3rdparty - fgfs-win32-VS100-3rdParty+OSG-20120411.zip 

\install\msvc100\OpenSceneGraph - archive.zip, after 
removing the initial 'archive/' folder... 

And (mostly) following the Fred/Gijs cmake wiki... 

Built and installed Release SG in 
\install\msvc100\SimGear 
so pointed to that when building FG... 

Built c:\FG\14\build-fg\src\Main\Release\fgfs.exe 

After adding the path - 
c:\FG\14\install\msvc100\OpenSceneGraph\bin 
to my PATH environment variable, this ran well in 
normal mode, no problems, but no rembrandt shadows 
on a trial of that... but that can wait... all else 
worked well in the few simple flights done... 

So what 3rdparty stuff did you use? What was your 
command line? What exactly was the console 
output? 

Then we MAY be able to help more... 

Regards, 
Geoff. 




------------------------------------------------------------------------------ 
For Developers, A Lot Can Happen In A Second. 
Boundary is the first to Know...and Tell You. 
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! 
http://p.sf.net/sfu/Boundary-d2dvs2 
_______________________________________________ 
Flightgear-devel mailing list 
Flightgear-devel@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/flightgear-devel 
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to