Hi Mo,
What did you figure out?
Also, do I have to set up a campaign even if I’m only interested in revenues and not cross promotion?
Thanks!
Hi,
What I was talking about was that the fact that I was not getting ads because I did not start a campaign! I am not testing cross promotion so yes you need to start a campaign to get revenues from installs.
Hope this help.
Mo
@Renato: Are you by any chance using the timed_chartboost_show_ad()???
If yes you may need to use show_ad() when you want to show an ad. In my case I have the code above (first post) in my main.lua BUT use show_ad() (not timed) in game over module. Time to time I do not see any ads but it is because they were none at the time. After a while I see ads again.
I hope we can figure your issue.
Mo
what I really don’t get is why my installs do not get paid. maybe its an android permission thing?
does sample app works for you guy ?
does it work on corona simulator or only on devices ?
any known problems on devices (both ios or android) ?
Regards
Tom
@Bldko: It seems to work fine for me. Not sure why it won’t for some people like Renato. It works both in simulator (PC and mac) as well as in the devices (iphone5, iphone4 and ipad2 all OS 6+) I believe the notes says that It won’t work for OS 5 so watch that for that. All i did was to copy/past the code above (in my main.lua) , start a campaign and use show_ad() (not the timing one) in my gameOver.lua. I do not get 100% fill rate but not bad. My plan is to combine it with Revmob (and maybe even with Tap for Tap) so pretty much no matter what people will see an ad. Need more work on this implementation.
In short, yes it works for ME!
Hope this help.
Mo
ps: As I said before, I am using my Space Command ID (which is a live app) for it but my code is not integrated yet in Space Command. Not sure if that makes a difference.
Here a screenshot of the ad showing on the simulator (on a Mac but not the xcode sim)
Mo
ok i made it working, this is list of steps you must do based on sample code from https://github.com/ChartBoost/corona-sdk
- download sample SDK
- create chartboost profile
- create new app
- copy its ID and its secret into your sample code
- check app version and proper bundleID
- Setup app in chartboost profile
- set test mode first
- set landscape or portrait
- create publisher campaign for this app
- add a test device to this campaign
- run your app in corona simulator, should show test ad unit, remember that orientation is important
- compile for device, remember about same bundleID
- test on device, should show test unit
- turn off test mode in chartboost profile
- should show ad unit
- remember that in some countries / areas there are little campaigns so no ads will be displayed
- in Poland there are no ads
- i used US IP and i have plenty of different ads
- make a test installation on a device by clicking ad and install an app
- service is not real time so it will be recorded after some time (12 hours or so) in the dashboard
- always use preload ad unit if possible
- the end
Btw i found a bug
- If you show ad unit there a nice fade in the background gray from alpha 0 to alpha 1
- if you close ad unit there is no fade out in the background gray from alpha 1 to alpha 0, this is Corona bug with overlay scene-board
- speed of ad unit movement is very slow how to speed it up ?
Tom
Thanks Tom for writing out the steps, that was helpful.
You’re right about the background gray not fading out smoothly, I’m seeing the same issue.
Is anyone else also seeing an issue with letterbox scaling (not with the ultimate config.lua, just plain-old letterbox scaling)? In letterbox scaling, the grey background won’t fill the whole screen, only the area from (0,0) to (display.contentWidth,display.contentHeight). Instead I think it needs to go from (display.screenOriginX,display.screenOriginY) to (display.contentWidth-display.screenOriginX,display.contentHeight-display.screenOriginY).
- Andrew
EDIT: I solved this by adjusting my config.lua. Instead of this:
[lua]
application =
{
content =
{
width = 320,
height = 480,
scale = “letterbox”,
fps = 60,
imageSuffix =
{
["@2x"] = 1.5,
["@4x"] = 3.0,
},
},
}
[/lua]
I now do this
[lua]
application =
{
content =
{
width = 320 * (display.pixelHeight/display.pixelWidth>1.5 and 1 or 1.5/(display.pixelHeight/display.pixelWidth)),
height = 480 * (display.pixelHeight/display.pixelWidth<1.5 and 1 or (display.pixelHeight/display.pixelWidth)/1.5),
scale = “letterbox”,
imageSuffix =
{
["@2x"] = 1.5,
["@4x"] = 3.0,
},
},
}
[/lua]
This has the benefit of always making screenOriginX,screenOriginY equal to 0,0 and display.contentWidth,display.contentHeight equal to the appropriate content dimensions for letterbox.
1- Yes I can see that it is fade in when showing but fade out when i hide it. Not too critical at this time.
2- I also see that the gray out do not fill up the all screen (see my screenshot above). In my case it hides all the buttons so again not critical at this point but I would really prefer a full screen coverage of the gray out area. But how? I guess one way is to use the listener and draw a rectangle that would cover the all screen (with a touch event that go no where) and then use the listener to hide the faded rectangle when the ad is closed or touched…
I am glad more people are experimenting with it!
Mo
cool! Your config does cover the all screen BUT in my case, all my assets are zoomed when I use your config. I am using ipad (1024/768 landscape) but also want to target iphone4,4s,5 and ipad2,3,4 Right now I am using:
[lua]
application =
{
content =
{
width = 768,
height = 1024,
xAlign = “center”,
yAlign = “center”,
scale = “letterBox”,
antialias = false,
launchPad = false,
audioPlayFrequency = 44100,
fps = 60,
imageSuffix =
{
["@2x"] = 1, – for iPhone, iPod touch, iPad1, and iPad2
["@4x"] = 2, – for iPad 3, ipad 4
},
},
}
[/lua]
EDIT 1: If I use: (my base screen is 768/1024 (landscape)
width = 768 * (display.pixelHeight/display.pixelWidth>1.5 and 1 or 1.5/(display.pixelHeight/display.pixelWidth)),
height = 1024 * (display.pixelHeight/display.pixelWidth<1.5 and 1 or (display.pixelHeight/display.pixelWidth)/1.5),
The assets are back to normal but then the Chartboost gray area won’t cover the all screen anymore…
EDIT 2: using this:
width = 640 * (display.pixelHeight/display.pixelWidth>1.5 and 1 or 1.5/(display.pixelHeight/display.pixelWidth)), height = 960 * (display.pixelHeight/display.pixelWidth<1.5 and 1 or (display.pixelHeight/display.pixelWidth)/1.5),
It seems to be better (not perfect) but at least I do not get a zoom effect AND the Chartboost covers the all screen. I can see I need to re-adjust some of my assets but most of them are fine (i.e.: buttons…)
THANKS!!!
Hi Mo,
If you’ve set up your project with an assumption of 1024,768, then you should be able to modify my example config.lua to work. Replace the 320 with 768, replace the 480 with 1024, and replace the 1.5’s with 1.33333333333 (or better yet, 4/3, to avoid any rounding).
- Andrew
Hmm, somehow my reply went higher up in this thread. Here it is again so it’s at the bottom, easier to see the conversation:
Hi Mo,
If you’ve set up your project with an assumption of 1024,768, then you should be able to modify my example config.lua to work. Replace the 320 with 768, replace the 480 with 1024, and replace the 1.5’s with 1.33333333333 (or better yet, 4/3, to avoid any rounding).
- Andrew
EDIT: OK, my posts were actually going to the bottom, it just wasn’t displaying right in my browser until I refreshed.
Thanks Andrew. I made the changes and my graphics look good again. BUT right now Chartboost stopped feeding me ads so I have to wait they re-start again! When it happens I will be able to tell if the gray area fill up the screen or not. I will keep you posted as soon I can get an ad again…
Mo
I not succeed in putting the chartboost code to work last week. Today, I just ran the same code it started working. So, maybe Chartboost needed some time to enable my campaign…
Yaaa! Great to know. Yes sometimes the app do not show ads for 30 mn to 1 hours but then it comes back and show almost at every game over. My guess, this is due to the fill rate not being 100%. Still a week is long time! When I first try it, the first ad I think show up pretty quickly (at least after I figure out that up I need it start a compaign!) Good news Renato. Mo
Hi :
I just spend all day try chartboost today .
Here is my personal result. (My country is in Asia)
The fill rate of Android are not very good out side of America (Compare with Revmob ) . Today I try it on 5 android devices. first , it show ads ok . after 1 hour it always show
Chartboost: shouldRequestInterstitial Default?
Chartboost: didFailToLoadInterstitial Default?
I spend a lot time to find what’s going on . after few hours , it working again for maybe 30 mins .
In iOS , the status is better then Android .
Tonight . I try it via US VPN . It work fine . even on Corona simulator it works.
I really no idea what’s the rule . all I can sure that iOS in USA will be work well .
So, If I suggest others have backup ads solution on android app out side of USA , If Chartboost fail to load ads . you can switch to other ads.
Thank you all for sharing and posting your experiences here. I’m finally getting around to incorporating Chartboost, and the sample code up top on the first page, as well as step by step things to do, plus things to look out for and different experiences – they really helped. I got mine up and working… some what.
The problem I have, though, is for interstitial ads. I don’t see how we may get the callback from the Chartboost. On Chartboost website, under Campaign > Network Publishing Campaign > Advanced Settings, I see a mention of callbacks, but I’m not sure if it’s integrated with chartboost-corona-sdk. I grabbed it from github today, but I don’t see any mention of the callback listener anywhere.
I need a callback listener to let my app know whether or not (1) ad was served (if it’s not filled, I’d show another ad), and (2) user closed the ads or clicked on the ads (based on which my app would advance to the next screen.) Without the callback to let me know the #2, my app just end up hanging.
I thought of using timer to auto-advance to the next screen (or immediately after showing ads, advance the screen), but it looks terrible, because it ends up showing the next screen behind the ad. I guess if the interstitial ads are truly full screen, it would not be an issue, but with Nexus 7, it really isn’t full screen. (And I suspect many Android device will have the same issue. I haven’t checked iOS version yet, though.)
So how do we deal with this?
Naomi
Hi Naomi,
The callbacks referred to on the website are a different concept.
For callbacks with your app, use the “delegates” (another word for callback) described in the GitHub page: https://github.com/ChartBoost/corona-sdk. You have to register your delegates when you setup the ChartBoost session, instead of each time you make an ad request.
- Andrew
Hey, Andrew @aukStudios, thank you for letting me know. That’s really helpful.
So, do I do something like this:
[lua]
local function doThisThingNow()
– advance to the next screen
end
local delegate = {
didCloseInterstitial = function(location) print("Chartboost: didCloseInterstitial " … location); doThisThingNow; return end,
}
[/lua]
Naomi
Edit: while editing my post, hitting tab or enter ended up posting it before I finished writing it up. Oh well…
Edit 2: And yeah, I see. I read the usage #4 on github, and it’s pretty clear what to do. Thanks again, Andrew, for pointing it out for me.