Understanding Rembrandt: Difference between revisions

Jump to navigation Jump to search
Line 1: Line 1:
== Background ==
== Background ==
Many of us are wondering why Rembrandt is so slow for us, despite having fairly powerful computers.  
Many of us are wondering why Rembrandt is so slow for us, despite having fairly powerful computers.
 
 
{{FGCquote
|1= there’s plenty of other people with reasonable hardware who have problems with Rembrandt performance - me for example :) And while that may be related to settings, being a lay Mac user I don’t like solutions which require extensive configuration to give acceptable performance.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/31687794/
  | title  = <nowiki>Re: [Flightgear-devel] Rendering strategies</nowiki>
  | author = <nowiki>James Turner</nowiki>
  | date  = Nov 27th, 2013
  | added  = Nov 27th, 2013
  | script_version = 0.23
  }}
}}
 
{{FGCquote
|1= with a i3770K and a GTX670, I get some hit from ALS (10-30%) but Rembrandt instantly drops me to 20fps, and < 10fps I use an aircraft I actually want to fly (777 or Citation) and go to any major airport (EGKK, EHAM, EDDM, EDDF, EGLC, VHHH) This is at 2560x1600, but on the 670 I would be highly surprised if I'm fill-rate limited, given that AA is off, and the general suboptimal sie of our primitive batches. Emilian has explained on IRC this might be due to the out-of-the-box / default config for Rembrandt being highly suboptimal, which I didn't yet evaluate, I would be delighted to have it more usable. I'm going to test further over the weekend.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/31075172/
  | title  = <nowiki>Re: [Flightgear-devel] reminder: entering feature freeze now</nowiki>
  | author = <nowiki>James Turner</nowiki>
  | date  = Jun 20th, 2013
  | added  = Jun 20th, 2013
  | script_version = 0.23
  }}
}}


== Objective ==  
== Objective ==  

Navigation menu