Hi everyone,

Installed GPL and GEM+ using the easy installation guide. Game is working okay, but when launching through GEM+ there is black boxes up and down scren when using 1920x1080 resolution. With opengl v2 I have problem that when I go driving I have a transparent black box in my right side of the screen also. With direct 3d v2 there is no problem.

I fixed that up and down screen black boxes with letterbox v3 fix.

I want to know is the opening screen of the game and options,driver profiles etc. always like 640x480 and then 1920x1080 only in when you are racing? Cause mine are.
I have set in GEM+ custom resolution to 1920x1080 and in game also. At the moment it seems direct 3d v2 is better for me but it seems strange cause almost everyone is using opengl v2.  
What is that transparent black box in open glv2 mode when driving? Does anyone else have it?  

My setup is Win10, 16gb ram, gtx 1070, intel i7 4770 3,4ghz..monitor is sony's 40" led tv 1920x1080.
I drive with fanatec csr wheel with csp elite pedals. ( mostly hugging fences in this game)

my wheel keeps defaulting to an older logitech wheel (the blue one ) in the logi profilier ( lgs 510 x64 )

in the past i would just uninstall reinstall the profiler that would fix the problem

but now when i do that all i get is the blue wheel

i think i read somewhere on here someone had the same thing happen but i couldnt find it

I was scrolling winehq.org for the latest Wine 1.9.19 release and found:

What's new in this release:

• Initial version of a udev bus driver for HID.
  
• Various improvements in joystick support.

So I took my old PC and installed Linux Mint 18 and then wine,

added jstest-gtk for the mappings of my G27.

I installed GPL from the CD with installer 1.07 and GEM2 package.

Success! Doing a lap in Monza gave me a big smile! this ffb is as smooth as in W7!
I use ffb2 checked in GEM+ with 0-0-250 forces.

The only downside for me is that the new linux kernels are no longer AMD compatible...
Last year the kernels wich allowed to run proprietary AMD drivers fglrx worked perfect!

This time I had to use the build in drivers wich do not support OGL, but D3D7V2 works ok...

If You have an NVidia GPU you can use  their proprietary drivers and will get a perfect GPL on a free OS!

So I have to wait some time until AMD supports the actual kernel again

Everything has been fine with GPL for ages, changed mods via Gem occasionally, etc.  A couple of weeks ago my vid card, an aging 5670, died;  installed an even older 8500GT while deciding on a replacement and reverted to a smaller monitor - 1440x900 - for the interim.  Changed all games settings accordingly.  GPL still working fine; though a couple of other games stopped working (arcade game "Egyptoid" - log file states,  "! Error ! D3DCREATE_HARDWARE_VERTEXPROCESSING" - and a favorite fps "No One Lives Forever 2", no messages just locks up when loading a save).

Installed the new vid card, GTX950, this past weekend and returned to the 1080 monitor.  All seemed well with GPL til I tried to change from the F2 mod back to the F1 cars, all fields in Gem+ changed appropriately, game started, got to the "driver info, team info, etc.", clicking to proceed gets a CTD with that useless windows message "the instruction at 'blah,blah' referenced memory at...".  Tried again, same result.  Tried returning to the F2 mod, which had been working just a couple of hours earlier, and Gem says it is rebuilding the F2 exe, then crashes with a simple "error" window

 gem.png   532.42K   14 downloads

Clicking OK there does nothing.  Repeatedly clicking OK, about a dozen times, gets

 gem_4.png   17.97K   17 downloads

I OK that and Gem closes.

If I start Gem and close it without doing anything else, I get

 gem_3.png   35.26K   13 downloads

Select "No" and Gem closes, select "Yes" and it's back to the error box.

Debug.txt will show:
"*** Error Message ***
Patching errors found for j:\sierra\gpl\gplc65.exe"
though the .exe listed is different each time (as are the .exe files present in GPL).

The first time I checked Gem's logs there was something about "...procedure call to app", but I didn't think to copy that and it was overwritten.

The patch log contains:
"OpenExe: Couldn't open j:\sierra\gpl\gpl_f3.exe
The process cannot access the file because it is being used by another process.

PatchWithData: No executable is currently open for patching
PatchWithData: No executable is currently open for patching
PatchWithData: No executable is currently open for patching
-(repeated numerous times)-

PatchWithXml: No executable is currently open for patching
PatchWithXml: No executable is currently open for patching
PatchWithXml: No executable is currently open for patching
-(repeated numerous times)-

UpdateResourceStringA: No executable is currently open for patching
SaveExe: No executable is currently open for patching
-(repeated numerous times)-"

I tried deleting all but the original gpl.exe so Gem would rebuild everything, but it just results in the same string of events.

I mentioned those other games because I had a similar issue years ago cured by installing the "DX9c redist" files (yes, DX10, 11, etc. are backwards compatible but many older games are not "forward compatible", they are looking for a DX install but newer DX versions are integral to windows, not individual installs ...at least that is how a programmer described the situation).  So I tried another DX9 reinstall;  it shows copying a handful of files then says it is done ...but nothing changes.  In fact I can run that installer repeatedly and it shows copying those same files each time.

(FWIW, Egyptoid only requires DX8;  NOLF2 is even older and is known for being picky about vid drivers.)

While driving around Monaco today I noticed a few issues with mip files not having their invisible color set.  Some were within the original Papyrus monaco.dat file (not updated by Monaco Rocks!) and another was an actual Monaco Rocks! mip file.  Here are the fixes.