The gpu.bind function has a parameter reset, which defaults to true.
http://ocdoc.cil.li/component:gpu
This parameter... isn't in OCEmu.
This more or less means that any code that binds GPUs a lot tested on OCEmu may encounter issues when run on actual OC due to the change from not-resetting to resetting.
(Programs which rely on the resetting behavior are less of an issue.)
(EDIT: Sorry about the rather sparse issue, hit the publish button too early. Example program/eeprom that shows a difference on OCEmu (Resolutions are unchanged) vs. OC (Screens end up with resolution available via last GPU), added. Point is to give an idea of where things could go wrong.)
-- get information about GPU capabilities
local i = 1
for ad in component.list("gpu") do
local a = component.proxy(ad)
for b in component.list("screen") do
a.bind(b) -- missing , false
a.setForeground(0xFFFFFF)
a.setBackground(0)
local w, h = a.maxResolution()
a.set(1, i, w .. ", " .. h)
end
i = i + 1
end
while true do computer.pullSignal() end
The
gpu.bindfunction has a parameterreset, which defaults to true. http://ocdoc.cil.li/component:gpu This parameter... isn't in OCEmu. This more or less means that any code that binds GPUs a lot tested on OCEmu may encounter issues when run on actual OC due to the change from not-resetting to resetting. (Programs which rely on the resetting behavior are less of an issue.) (EDIT: Sorry about the rather sparse issue, hit the publish button too early. Example program/eeprom that shows a difference on OCEmu (Resolutions are unchanged) vs. OC (Screens end up with resolution available via last GPU), added. Point is to give an idea of where things could go wrong.)