I haven’t released any apps with Chartboost yet, but do you have the delegate methods “shouldRequestInterstitial” and “shouldRequestInterstitialsInFirstSession” in your delegate table? (both should return true).
If you don’t, then I could imagine that it could affect the SDK install count.
Just guessing though…
@ingemar, yes - I have all those delegate methods, although most of them I left empty as I use only “didDismissInterstitial” one.
OK, sounds good. The important thing is that both delegates return “true;”.
Some other things I can think of is that cb.startSession() must be called both on “applicationStart” and “applicationResume”.
Also in chartboost.create() I saw in their sample code that they wanted the app bundle id (com.company.appname).
I don’t know if it’s 100% necessary, but I include it in my call anyway:
chartboost.create{ appId = CHARTBOOST\_APPID[directives.STORE].ID, appSignature = CHARTBOOST\_APPID[directives.STORE].SIG, delegate = chartboostDelegate, appVersion = settings.version, appBundle = flags.bundleid };I don’t want to hijack this thread, but anyone else experiencing such low numbers?
37840 impressions (Fullscreen), 878 Clicks, 28!!! installs…
makes 22$.
Thanks for all the tips, but it’s all set up here as you describe.
So the delgate methods return true, I call cb.startSesson()
on start (calling it once in main.lua body) and on resume: (calling it on system event == onApplicationResume).
Also I provided app bundle id, and even version.
I have no idea why this is not working properly 
can’t say about the revenue numbers as I don’t have any yet,
but what about your install SDK to itunes real installs ratio?
Do you get similiar numbers? Thanks
I’m planning to go live some time next week. I’m mixing Chartboost/Revmob/Vungle, I’ll post my numbers once I have sufficient data to report…
I forgot to mention that this is android.
it says 60’000 installs, which is true.
Quote from Github:
“The Chartboost start session call, cb.startSession(), must be called every time your app becomes active (on both hard and — for iOS games — soft bootups)”
I left that call out in event.type == “applicationResume” and the ads still served up. Still, I should know better as I knew about the quote above. Maybe my installs won’t count…
I’ll reject the binary right now (seeing as it only went in this morning) and add:
cb.startSession()
cb.cacheInterstitial()
cb.cacheMoreApps()
to event.type == “applicationResume”
Incidentally the caching doesn’t seem to make much different in my testing. Particularly for the more apps wall.
I sincerely hope Chartboost performs better than RevMob as I’ve seen over 400 clicks on RevMob since my last install. I’m sure the RevMob site states somewhere that you can expect an install every 100-200 clicks. At least I have iAds to fall back on…
Best,
Martin.
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).
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).
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).
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
Hi guys, Thank you guys for all the good info. Especially from you brave soul who already have an app live with Chartboost! One quick note. I have notice something about App signature in the example they give. Anybody know about that and if that could be any issue for counting downloads? I do not have my code in front of me but I only recall putting the app ID provided by Chartboost. Maybe I am wrong about this… ------ local appId = “4f7aa26ef77659d869000003” local appSignature = “ee759deefd871ff6e2411c7153dbedefa4aabe38”-------- ??? ------ Thanks! Mo
@Mo
I use both appID and appSignature.
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